> The PnP BIOS spec does not require any PnP device other than those
> REQUIRED FOR BOOT (ie. keyboard, video, mobo, disk) be configured.
> Configuration of everything else is OPTIONAL, and not covered by the
> spec (ie. the BIOS can configure other devices any way it wants too).
As my BIOS detects the SB32 card, I suppose in order to find bootable
devices, the system has to examine all devices first. I always
thought that "isolating" and configuring would happen at the same
time. Also, doesn't the BIOS make sure that there are not resource
conficts? If so, bootable devices that remain active after boot strap
will have resources that do not conflict with any other devices. 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.
Talking about PnP BIOS: There are different functions for boot
devices and the rest. The rest can be possibly obtained by reading
ESCD (if present). A PnP OS has the option to use and update ESCD
(Extended Setup Configuration Data, stolen from EISA). The BIOS would
respect these settings then (at least my BIOS (Award/Asus) updates
ESCD after hardware changes.
> There are really 3 relevant PnP specs here: PnP-ISA, Pnp-BIOS, and ESCD.
Anybody has a understandable ESCD spec? I'm lacking the EISA part...
>
> There is no mechanism for a device to request that it be ignored.
> By default, all devices are unconfigured and disabled. It is up to
> something else to configure and activate them.
>
> > 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.
Ulrich