Message-ID: <45D88D9F.7090705@zytor.com>
Date: Sun, 18 Feb 2007 09:32:15 -0800
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061219)
MIME-Version: 1.0
To: Jean Delvare <khali@linux-fr.org>
CC: 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
References: <1171479361.3706.48.camel@mentorng.gurulabs.com>	<Pine.LNX.4.64.0702141104210.3604@woody.linux-foundation.org>	<20070214202144.1ddb930f.khali@linux-fr.org>	<45D46F7B.3060105@zytor.com> <20070218170401.286e0fc6.khali@linux-fr.org>
In-Reply-To: <20070218170401.286e0fc6.khali@linux-fr.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 887
Lines: 23

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.

	-hpa
-
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/