From: Thomas Hood <jdthood@mail.com>
To: linux-kernel@vger.kernel.org
Subject: PnP BIOS driver status
Date: Fri, 08 Mar 2002 18:00:40 -0500 [thread overview]
Message-ID: <1015628440.14518.212.camel@thanatos> (raw)
A couple people have asked me about the status of the
PnP BIOS driver, so I thought I'd post an update.
History: During the pre-Tosatti 2.4-ac series the driver was
hammered into a reliable form. However it never entered the
mainline kernel series.
The driver was then stripped down to the core functionality
required to make the lspnp and setpnp utilities work.
pnpbios_register_driver() and pnpbios_unregister_driver() are
still there but aren't used by anything. Additional /proc/
interface files were then added to allow reading of ESCD info.
The latest version of the driver seems nice 'n' stable and can
be found in Alan's latest 2.4 patches.
Current 2.5 kernels also contain the driver, but it's a bit out
of date. There's a patch in 2.5-dj but that's also out of date.
("Out of date" here means "missing new features and some
cleanups".) Once DJ releases a 2.5.6-dj I'll send him a patch
to bring his tree up to date. Then he can pass it on to Linus.
--
Thomas Hood
next reply other threads:[~2002-03-08 23:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 23:00 Thomas Hood [this message]
2002-03-08 23:14 ` PnP BIOS driver status Dave Jones
2002-03-09 0:43 ` Thomas Hood
2002-03-09 1:00 ` Brian Gerst
2002-03-09 1:10 ` Thomas Hood
2002-03-09 2:23 ` Brian Gerst
2002-03-09 3:02 ` Thomas Hood
2002-03-09 1:25 ` Alan Cox
2002-03-09 1:37 ` Brian Gerst
2002-03-09 2:00 ` Alan Cox
2002-03-09 1:51 ` Brian Gerst
2002-03-09 2:26 ` Alan Cox
2002-03-09 2:24 ` Thomas Hood
2002-03-09 2:48 ` Thomas Hood
2002-03-09 14:44 ` Thomas Hood
-- strict thread matches above, loose matches on Subject: below --
2002-03-09 15:11 Thomas Hood
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=1015628440.14518.212.camel@thanatos \
--to=jdthood@mail.com \
--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