summaryrefslogtreecommitdiffstats
path: root/sys/ia64
diff options
context:
space:
mode:
authorjhb <jhb@FreeBSD.org>2005-10-31 18:31:16 +0000
committerjhb <jhb@FreeBSD.org>2005-10-31 18:31:16 +0000
commit9f7eef096f274e3e79f4f8a19c09b9d4d1f65036 (patch)
tree51a2c7b7befac11aed19c8d93e5de518e4638a2a /sys/ia64
parente9bc61e47f0d61a0c26a2c3e3adc857bbdb4925e (diff)
downloadFreeBSD-src-9f7eef096f274e3e79f4f8a19c09b9d4d1f65036.zip
FreeBSD-src-9f7eef096f274e3e79f4f8a19c09b9d4d1f65036.tar.gz
Some of the VIA pm and propm devices are actually the same device as the
PCI-ISA bridge. Thus, when viapm0 or viapropm0 attaches, isab0 dosen't attach so there is no isa0 bus hung off of that bridge. In the non-ACPI case, legacy0 will add an isa0 anyway as a fail-safe, but ACPI assumes that any ISA bus will be enumerated via a bridge. To fix this, call isab_attach() to attach an isa0 ISA child bus device if the pm or propm device we are probing is a PCI-ISA bridge. Both drivers now have to implement the bus_if interface via the generic methods for resource allocation, etc. to work. Also, we now add 2 new ISA bus drivers that attach to viapm and viapropm devices. PR: kern/87363 Reported by: Oliver Fromme olli at secnetix dot de Tested by: glebius MFC after: 1 week
Diffstat (limited to 'sys/ia64')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud