[idalton@ferret.phonewave.net]
> Multiple bus types... Compaq server with PCI and EISA, for example?
> IIRC the EISA bus is bridged onto one of the PCI busses. Perhaps a
> breadth-first scan; PCI busses first, then bridged devices on PCI,
> then internal non-PCI busses, then external busses.
No, bridging is transparent to most drivers, so this doesn't
necessarily make sense. The thing to do is just decree "drivers will
be registered in *this* order..." and then list the busses in some
arbitrary order, and specify some sub-scheme for enumerating drivers on
each bus.
...Which still doesn't solve the problem of multiple device types on a
single bus, for which I think my proposal (passing a meta-address of
some sort into scsi_register() and similar, and letting it sort devices
as they come in. (Until the end of the bootstrap, of course. Modules
all go in at the end.)
> Are there any systems where a non-PCI bus is not connected through a
> PCI-foo bridge?
There are lots of non-PCI systems out there. And quite a few, I
suspect, where PCI is bridged off the "native" bus rather than the
other way 'round.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jan 23 2001 - 21:00:18 EST