The BIOS is required to isolate all devices, but it doesn't have
to configure them all.
> Also, doesn't the BIOS make sure that there are not resource
> conficts?
Again, only on the devices required for boot.
> If so, bootable devices that remain active after boot strap
> will have resources that do not conflict with any other devices.
Again, only on the devices required for boot. Toss in another
device after boot (like a sound card) and you may have to reconfigure
EVERYTHING!
> As
> some devices are less flexible in the range of their resources (e.g.
> fixed I/O addresses) the BIOS would have to get a global overview
> over all the requirements.
The PnP specs assume a BIOS is simple (ie. stupid). Configuration
can be an NP complete problem (I think - it is at least difficult),
and adding a card can result in an UNBOOTABLE configuration! After
boot, an OS configuration manager can make any tough decisions.
> Anybody has a understandable ESCD spec? I'm lacking the EISA part...
Contact the EISA people then. I have the address (somewhere) if you need it.
> > > The idea to have to use isapnp and a sound
> > > module seems not the very best solution.
> > ^^^
> > Why won't isapnptools and a sound module work? (it doesn't work for me)
> > What will work?
>
> I hate autoloaded sound modules as long as the mixer settings are not
> persistent (maybe mixer settings should be passed on the command
> line) because I have sensitive ears.
I agree, so I load it without autoclean.
-- Andrew E. Mileski mailto:aem@netcom.ca