John Baldwin 4edef187b8 Add support for managing PCI bus numbers. As with BARs and PCI-PCI bridge ... I/O windows, the default is to preserve the firmware-assigned resources. PCI bus numbers are only managed if NEW_PCIB is enabled and the architecture defines a PCI_RES_BUS resource type. - Add a helper API to create top-level PCI bus resource managers for each PCI domain/segment. Host-PCI bridge drivers use this API to allocate bus numbers from their associated domain. - Change the PCI bus and CardBus drivers to allocate a bus resource for their bus number from the parent PCI bridge device. - Change the PCI-PCI and PCI-CardBus bridge drivers to allocate the full range of bus numbers from secbus to subbus from their parent bridge. The drivers also always program their primary bus register. The bridge drivers also support growing their bus range by extending the bus resource and updating subbus to match the larger range. - Add support for managing PCI bus resources to the Host-PCI bridge drivers used for amd64 and i386 (acpi_pcib, mptable_pcib, legacy_pcib, and qpi_pcib). - Define a PCI_RES_BUS resource type for amd64 and i386. Reviewed by: imp MFC after: 1 month		2014-02-12 04:30:37 +00:00
..
cardbus_cis.c	Partially revert 222753: If a CardBus card stores its CIS in a BAR, delete	2011-09-12 15:21:52 +00:00
cardbus_cis.h
cardbus_device.c
cardbus.c	Add support for managing PCI bus numbers. As with BARs and PCI-PCI bridge	2014-02-12 04:30:37 +00:00
cardbusreg.h
cardbusvar.h	Add support for managing PCI bus numbers. As with BARs and PCI-PCI bridge	2014-02-12 04:30:37 +00:00