From: "H. Peter Anvin" <hpa@zytor.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Jean Delvare <khali@linux-fr.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dax Kelson <dax@gurulabs.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linus' laptop and Num lock status
Date: Sun, 18 Feb 2007 16:26:41 -0800 [thread overview]
Message-ID: <45D8EEC1.4030203@zytor.com> (raw)
In-Reply-To: <20070218100644.e7c40a88.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> On Sun, 18 Feb 2007 09:32:15 -0800 H. Peter Anvin wrote:
>
>> Jean Delvare wrote:
>>> On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
>>>> Jean Delvare wrote:
>>>>> On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
>>>>> BIOS RAM is mapped at 0x400 so all we need to do is to one byte from
>>>>> RAM (offset 0x497). This is how Suse's hwinfo does.
>>>> Perhaps that's what Suse does, but the proper address is 0x417.
>>>>
>>>> 0x497 is the rarely-used LPT2 timeout counter.
>>> Still, the information printed by hwinfo is correct, I've tested it
>>> myself. Is there some publicly available documentation about the x86
>>> BIOS RAM mapping?
>>>
>> Google for Ralf Brown's Interrupt List.
>
> (Ralph)
>
> I didn't find the BIOS data areas/tables in Ralph's web pages...
>
It's called memory.lst in the Interrupt List.
-hpa
next prev parent reply other threads:[~2007-02-19 0:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 18:56 Linus' laptop and Num lock status Dax Kelson
2007-02-14 19:12 ` Linus Torvalds
2007-02-14 19:19 ` Dax Kelson
2007-02-14 19:21 ` Jean Delvare
2007-02-14 19:32 ` Linus Torvalds
2007-02-14 21:34 ` Dax Kelson
2007-02-14 21:58 ` Jan Engelhardt
2007-02-15 0:06 ` Krzysztof Halasa
2007-02-20 13:57 ` Helge Hafting
2007-02-15 0:31 ` Alan
2007-02-18 16:19 ` Jean Delvare
2007-02-15 14:34 ` H. Peter Anvin
2007-02-18 16:04 ` Jean Delvare
2007-02-18 17:32 ` H. Peter Anvin
2007-02-18 18:06 ` Randy Dunlap
2007-02-19 0:26 ` H. Peter Anvin [this message]
2007-02-18 17:54 ` Randy Dunlap
2007-02-14 19:26 ` Arjan van de Ven
2007-02-15 14:25 ` H. Peter Anvin
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=45D8EEC1.4030203@zytor.com \
--to=hpa@zytor.com \
--cc=dax@gurulabs.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.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.