hi,
by checking 2.4.18, I saw that "CONFIG_PNP" is not in use in the
source anymore except in Documentation/Configure.help and as a
variable that CONFIG_ISAPNP depends on.
=> remove.
as a side note, I'd want to know how linux is configuring
the PCI devices, when e.g. in the Bios Settings I say
"Yes - PNP aware OS installed".
reason I ask is because I get IRQ routing conflicts
with cardbus (PCI to PCMCIA bridge) / PC-Card Adapter / FlashRAM.
can also someone tell me which variable the "CONFIG_PNPBIOS" options
depends on? this seems to be another variable which is only
"used" on Documentation/Configure.help.
according to the documentation of "CONFIG_PNP", Linux configures
my Plug and Play devices. Alternatively ... the user space utils
from isapnptools. this sounds like linux does not configure
PCI devices and therefore, the "PNP Aware OS" should always be
set to "N" in the BIOS - is this correct?
/herp
> by checking 2.4.18, I saw that "CONFIG_PNP" is not in use in the
> source anymore except in Documentation/Configure.help and as a
> variable that CONFIG_ISAPNP depends on.
>
> => remove.
Hold on. This will change once the pnpbios driver
is merged. It's currently in Alan's tree (and in 2.5 stock).
> as a side note, I'd want to know how linux is configuring
> the PCI devices, when e.g. in the Bios Settings I say
> "Yes - PNP aware OS installed".
When you enable "PnP OS" in the BIOS, you are telling
the BIOS not to use PnP methods to configure PnP devices,
but to leave it to the OS to do the configuration.
> can also someone tell me which variable the "CONFIG_PNPBIOS" options
> depends on? this seems to be another variable which is only
> "used" on Documentation/Configure.help.
pnpbios is a driver used to communicate with the
PnP BIOS. This driver should be merged soon, but right
now only the help text for the driver is present in stock 2.4.
> according to the documentation of "CONFIG_PNP", Linux configures
> my Plug and Play devices.
In the case of ISA devices, Linux only configures them
if you have the isa-pnp driver built.
> Alternatively ... the user space utils
> from isapnptools. this sounds like linux does not configure
> PCI devices and therefore, the "PNP Aware OS" should always be
> set to "N" in the BIOS - is this correct?
The "PnP OS" boot flag may appropriately be set to 1
only Linux is prepared (by using the isa-pnp driver,
or isapnptools) to do PnP configuration itself.
Actually, I don't see why we should ever set the "PnP OS"
flag. It doesn't hurt to let the BIOS preconfigure
devices. Linux can always re-configure devices as it
sees fit, can't it?
--
Thomas Hood
> > by checking 2.4.18, I saw that "CONFIG_PNP" is not in use in the
> > source anymore except in Documentation/Configure.help and as a
> > variable that CONFIG_ISAPNP depends on.
> >
> > => remove.
>
> Hold on. This will change once the pnpbios driver
> is merged. It's currently in Alan's tree (and in 2.5 stock).
hm. this only adds to confusion.
> > as a side note, I'd want to know how linux is configuring
> > the PCI devices, when e.g. in the Bios Settings I say
> > "Yes - PNP aware OS installed".
>
> When you enable "PnP OS" in the BIOS, you are telling
> the BIOS not to use PnP methods to configure PnP devices,
> but to leave it to the OS to do the configuration.
and Linux is such an OS?
> > can also someone tell me which variable the "CONFIG_PNPBIOS" options
> > depends on? this seems to be another variable which is only
> > "used" on Documentation/Configure.help.
>
> pnpbios is a driver used to communicate with the
> PnP BIOS. This driver should be merged soon, but right
> now only the help text for the driver is present in stock 2.4.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> In the case of ISA devices, Linux only configures them
> if you have the isa-pnp driver built.
And If I have ISA-devices, which I have not.
> Actually, I don't see why we should ever set the "PnP OS"
> flag. It doesn't hurt to let the BIOS preconfigure
> devices. Linux can always re-configure devices as it
> sees fit, can't it?
As it seems, Linux cannot reconfigure devices, since only the
helptext for the driver is present, while a driver is
not present. At last not in 2.4. Only a dummy option
with a dummy help text *without even a note* that this is
not implemented!