John Baldwin a74d695299 Further relax the strictness of enforcing allocations to only come from ... decoded ranges. Pass any request for a specific range that fails because it is not in a decoded range for an ACPI Host-PCI bridge up to the parent to see if it can still be allocated. This is based on the assumption that many BIOSes are inconsistent/broken and that settings programmed into BARs or resources assigned to other built-in components are more trustworthy than the list of decoded resource ranges in _CRS. This effectively limits the decoded ranges to only being used for "wildcard" ranges when allocating fresh resources for a BAR, etc. At some point I would like to only be this permissive during an early scan of firmware-assigned resources during boot and to be strict about all later allocations, but that isn't viable currently. MFC after: 2 weeks		2011-12-29 16:23:14 +00:00
..
Osd
acpi_acad.c
acpi_battery.c
acpi_button.c
acpi_cmbat.c
acpi_cpu.c
acpi_dock.c
acpi_ec.c
acpi_hpet.c
acpi_hpet.h
acpi_if.m
acpi_isab.c
acpi_lid.c
acpi_package.c
acpi_pci_link.c
acpi_pci.c
acpi_pcib_acpi.c
acpi_pcib_pci.c
acpi_pcib.c
acpi_pcibvar.h
acpi_perf.c
acpi_powerres.c
acpi_quirk.c
acpi_quirks
acpi_resource.c
acpi_smbat.c
acpi_smbus.h
acpi_thermal.c
acpi_throttle.c
acpi_timer.c
acpi_video.c
acpi.c
acpiio.h
acpivar.h