summaryrefslogtreecommitdiffstats
path: root/release
diff options
context:
space:
mode:
authorpeter <peter@FreeBSD.org>1999-08-10 09:22:21 +0000
committerpeter <peter@FreeBSD.org>1999-08-10 09:22:21 +0000
commit8076722c425d631cf40c0f11bae560eec2d8cc35 (patch)
tree590bcbb35017fb3f5fa94f1eb4c94bc6fc53978d /release
parent8c9b3c8625c37d333fc8cb94e9ba6c2ee2fa2e12 (diff)
downloadFreeBSD-src-8076722c425d631cf40c0f11bae560eec2d8cc35.zip
FreeBSD-src-8076722c425d631cf40c0f11bae560eec2d8cc35.tar.gz
Hopefully fix the previous commit, it caused *all* bridges to be detected
as PCI->HOST bridges on my (440BX) box. My change is to remove the test at the beginning entirely, letting the switch on the device ID happen first. If the device ID is unknown, then (in the default case) check for the generic PCIS_BRIDGE_HOST tag. This should allow wierd cases (eg: wpaul's IMS VL bridge) to work by using the id override. This strategy is more in line with the other PCI match methods we use elsewhere, I only have a limited testbed, but having my USB etc devices detected as PCI->HOST bridges doesn't look good.
Diffstat (limited to 'release')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud