src-test2/sys/dev/pccbb, branch release/9.2.0

Merge r254306:

2013-08-15T12:19:16Z

Update PCI drivers to no longer look at the MEMIO-enabled bit in the PCI command register. The lazy BAR allocation code in FreeBSD sometimes disables this bit when it detects a range conflict, and will re-enable it on demand when a driver allocates the BAR. Thus, the bit is no longer a reliable indication of capability, and should not be checked. This results in the elimination of a lot of code from drivers, and also gives the opportunity to simplify a lot of drivers to use a helper API to set the busmaster enable bit. This changes fixes some recent reports of disk controllers and their associated drives/enclosures disappearing during boot. Submitted by: jhb Reviewed by: jfv, marius, adrian, achim Approved by: re

MFC: r227309 (partial)

2013-03-09T02:36:32Z

Mark all SYSCTL_NODEs static that have no corresponding SYSCTL_DECLs. The SYSCTL_NODE macro defines a list that stores all child-elements of that node. If there's no SYSCTL_DECL macro anywhere else, there's no reason why it shouldn't be static.

MFC r238954 - Restore the PCI bridge configuration upon resume.

2012-09-09T20:13:11Z

This allows my TI1510 cardbus/PCI bridge to work after a suspend/resume, without having to unload/reload the cbb driver. PR: kern/170058

MFC r226173, r227843, r227848 and r227908:

2011-12-31T14:12:12Z

Use DEVMETHOD_END to mark end of device methods. Remove superfluous device methods. Add some missing __FBSBID() macros.

Mark the card as bad on shutdown. This means that bus_child_present

2011-06-21T03:05:17Z

will return false on shutdown and massive spewage from usb disappears for usb cardbus adapters.

More expeirmentation suggests that 10ms isn't as reliable as

2011-06-18T03:16:51Z

previously thought, but 100ms seems to be. Likely there's a good middle ground, but for now be conservative.

After we get a good power signal, always wait about 10ms before

2011-06-18T02:25:08Z

proceeding. On boot, some laptops with certain cards in them sometimes fail on boot, but if the card is inserted after boot it works. Experiments show that small delays here makes things more reliable. It is believed that some combinations need a little more time before the power on the card is really stable enough to be reliable once the power is stable in the bridge.

sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.

2011-01-12T19:53:56Z

Commit the rest of the devices.

Temporarily revert the new-bus locking for 8.0 release. It will be

2009-08-20T19:17:53Z

reintroduced after HEAD is reopened for commits by re@. Approved by: re (kib), attilio

Make the newbus subsystem Giant free by adding the new newbus sxlock.

2009-08-02T14:28:40Z

The newbus lock is responsible for protecting newbus internIal structures, device states and devclass flags. It is necessary to hold it when all such datas are accessed. For the other operations, softc locking should ensure enough protection to avoid races. Newbus lock is automatically held when virtual operations on the device and bus are invoked when loading the driver or when the suspend/resume take place. For other 'spourious' operations trying to access/modify the newbus topology, newbus lock needs to be automatically acquired and dropped. For the moment Giant is also acquired in some key point (modules subsystem) in order to avoid problems before the 8.0 release as module handlers could make assumptions about it. This Giant locking should go just after the release happens. Please keep in mind that the public interface can be expanded in order to provide more support, if there are really necessities at some point and also some bugs could arise as long as the patch needs a bit of further testing. Bump __FreeBSD_version in order to reflect the newbus lock introduction. Reviewed by: ed, hps, jhb, imp, mav, scottl No answer by: ariff, thompsa, yongari Tested by: pho, G. Trematerra , Brandon Gooch Sponsored by: Yahoo! Incorporated Approved by: re (ksmith)