summaryrefslogtreecommitdiffstats
path: root/sys/dev/aacraid/aacraid.c
diff options
context:
space:
mode:
authorjhb <jhb@FreeBSD.org>2014-03-11 14:33:42 +0000
committerjhb <jhb@FreeBSD.org>2014-03-11 14:33:42 +0000
commitc157604f42c4e16d9aa5752902f75fdc5c38dfe3 (patch)
tree253b667fea78f095923e934e3fb24a5c63c98c07 /sys/dev/aacraid/aacraid.c
parentcc2de0e8574fc5877a2e35adf4e4a18dc65e9a73 (diff)
downloadFreeBSD-src-c157604f42c4e16d9aa5752902f75fdc5c38dfe3.zip
FreeBSD-src-c157604f42c4e16d9aa5752902f75fdc5c38dfe3.tar.gz
MFC 261243:
Some BIOSes incorrectly use standard memory resource ranges to list the memory ranges that they decode for downstream devices rather than creating ResourceProducer range resource entries. The result is that we allocate the full range to the PCI root bridge device causing allocations in child devices to all fail. As a workaround, ignore any standard memory resources on a PCI root bridge device. It is normal for a PCI root bridge to allocate an I/O resource for the I/O ports used for PCI config access, but I have not seen any PCI root bridges that legitimately allocate a memory resource.
Diffstat (limited to 'sys/dev/aacraid/aacraid.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud