summaryrefslogtreecommitdiffstats
path: root/contrib/libc++/src
diff options
context:
space:
mode:
authorjhb <jhb@FreeBSD.org>2014-01-28 20:53:33 +0000
committerjhb <jhb@FreeBSD.org>2014-01-28 20:53:33 +0000
commita638f0acf5d968ce554741250a31cf64703d7f22 (patch)
tree3a521aef52a0172fcab67bcda4012b7b07562bd5 /contrib/libc++/src
parent5c066f64123bc86c10537ae180565c8766e3cc2c (diff)
downloadFreeBSD-src-a638f0acf5d968ce554741250a31cf64703d7f22.zip
FreeBSD-src-a638f0acf5d968ce554741250a31cf64703d7f22.tar.gz
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. Reviewed by: jkim MFC after: 1 week
Diffstat (limited to 'contrib/libc++/src')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud