From: wingel@hog.ctrl-c.liu.se (Christer Weinigel)
To: dwmw2@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: reading/writing CMOS beyond 256 bytes?
Date: Mon, 9 Jul 2001 16:24:56 +0200 (CEST) [thread overview]
Message-ID: <20010709142456.C756436F9C@hog.ctrl-c.liu.se> (raw)
In-Reply-To: <19706.994679164@redhat.com>
In-Reply-To: <Pine.LNX.3.95.1010706094624.519A-100000@chaos.analogic.com>
In article <19706.994679164@redhat.com> you write:
>root@chaos.analogic.com said:
>> Motherboard manufacturers who have rewritable BIOS chips now leave one
>> page (typically 64k) for startup parameters. This is erased and
>> written using the magic provided by the chip vendors.
>
>You often have to do chipset-specific magic to enable the WE and Vpp lines
>to BIOS flash chips. See drivers/mtd/maps/l440gx.c in my working tree for
>an example.
Another way might be to use the PnP BIOS to read and write the
ESCD tables. I wrote some code to do this a few years ago and
after beating up the code a bit more I can at least read the ESCD
tables from the BIOS. If anyone is interested in doing something
with the code it can be found at:
http://acolyte.hack.org/~wingel/escd/
The advantage of using the PnP BIOS is that the PnP BIOS knows
about the format of the data in BIOS and how to do all the
chipset specific stuff. The disadantage is as usual that a lot
of BIOSes are buggy.
/Christer
--
"Just how much can I get away with and still go to heaven?"
next prev parent reply other threads:[~2001-07-09 14:35 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 [this message]
2001-07-06 15:07 ` Alan Cox
2001-07-08 18:28 ` ESCD Support for 2.4.6-ac1/PNPBIOS (was: reading/writing CMOS beyond 256 bytes?) Gunther Mayer
2001-07-08 18:35 ` 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=20010709142456.C756436F9C@hog.ctrl-c.liu.se \
--to=wingel@hog.ctrl-c.liu.se \
--cc=dwmw2@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.