* abs@netbsd.org [2000-10-18 11:02:27]
| 	Shouldn't that code fail the second attach with a diagnostic
| 	rather than panicing?

Perhaps.  Without understanding the bus code better I can't see a way
for the routine to fail (which would seem desirable).

The shark code which corresponds to this doesn't appear to have any
hangups about multiple ISA busses, but it does use a single static tag
to follow things around.  That would appear to be broken if the shark
ever actually acquired multiple ISA buses.  Probably the shark is
sufficiently limited in expansion capability and system variety that
this is never a problem.

I wonder what is attached to the second ISA bus (if it really
exists).  Perhaps more importantly, how would one get access to the IO
ports of the devices there ?

dme.