From: Gunther.Mayer@t-online.de (Gunther Mayer)
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Gregory (Grisha) Trubetskoy" <grisha@ispol.com>
Subject: ESCD Support for 2.4.6-ac1/PNPBIOS (was: reading/writing CMOS beyond 256 bytes?)
Date: Sun, 08 Jul 2001 20:28:19 +0200 [thread overview]
Message-ID: <3B48A643.124AA832@t-online.de> (raw)
In-Reply-To: <E15IXCD-0004Uu-00@the-village.bc.nu>
Hi,
with a litte patch to linux-2.4.6ac1 (which includes PNPBIOS)
the ESCD data is easily accessible.
Then "lsescd" will verbosely decode /proc/bus/pnp/escd.
This lets you access important info which would be beneficial for correctly
configuring PnP in Linux (e.g. when you set an IRQ to "reserved for legacy ISA"
in your BIOS setup or you can see what's the difference between selecting
"_PNP OS_" to yes/no in your BIOS setup screen).
Regards, Gunther
P.S. There is an additional potential benefit for ISAPNP: you can
get the PNP Port configured by your BIOS. Previously all cards had
to be reset to use a new port. Linux suffers serverly from not
doing PnP failsafe, burdening configuration tasks onto the user.
cat /proc/bus/pnp/pnpconfig_info
Revision=1 No_Csn=1 ISAPNP_Port=0x20b
^^^
Download from:
http://home.t-online.de/home/gunther.mayer/lsescd-0.10.tar.bz2
Alan Cox wrote:
>
> > Unfortunately, it seems that some settings are not in the 128 (or 256)
> > bytes accessible this way, so they must be stored elsewhere.
>
> Large numbers of BIOS settings are in the NVRAM ESCD area in modern systems
> (EISA config, ISAPNP config, etc)
>
> > Does anyone know where I should look for the remaining parts of CMOS
> > (short of having to sign some NDA with Intel?)?
>
> The PnPBIOS and ESCD specs are publically available if a little impenetrable
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-07-08 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 12:38 reading/writing CMOS beyond 256 bytes? Gregory (Grisha) Trubetskoy
2001-07-06 12:47 ` Peter Svensson
2001-07-06 14:30 ` Richard B. Johnson
2001-07-09 11:46 ` David Woodhouse
2001-07-09 14:24 ` Christer Weinigel
2001-07-06 15:07 ` Alan Cox
2001-07-08 18:28 ` Gunther Mayer [this message]
2001-07-08 18:35 ` ESCD Support for 2.4.6-ac1/PNPBIOS (was: reading/writing CMOS beyond 256 bytes?) Jeff Garzik
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=3B48A643.124AA832@t-online.de \
--to=gunther.mayer@t-online.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=grisha@ispol.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