From: Thomas Hood <jdthood@mail.com>
To: linux-kernel@vger.kernel.org
Cc: Herbert Rosmanith <herp@wildsau.idv-edu.uni-linz.ac.at>
Subject: Re: please remove CONFIG_PNP, CONFIG_PNPBIOS
Date: 26 Feb 2002 19:37:53 -0500 [thread overview]
Message-ID: <1014770275.6708.244.camel@thanatos> (raw)
> 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
next reply other threads:[~2002-02-27 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 0:37 Thomas Hood [this message]
2002-02-27 0:49 ` System Operator
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 22:43 Herbert Rosmanith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1014770275.6708.244.camel@thanatos \
--to=jdthood@mail.com \
--cc=herp@wildsau.idv-edu.uni-linz.ac.at \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®