From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dax Kelson <dax@gurulabs.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jean Delvare <khali@linux-fr.org>
Subject: Re: Linus' laptop and Num lock status
Date: Thu, 15 Feb 2007 06:25:00 -0800 [thread overview]
Message-ID: <45D46D3C.3010407@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702141104210.3604@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Wed, 14 Feb 2007, Dax Kelson wrote:
>> Are there any technical or political reasons why kernel can't change
>> from "force off" to "Follow BIOS"?
>
> How would you query it? I'm not even 100% sure that you can on all
> keyboards. We never query the leds, we always set them. I think. I don't
> know of any AT kbd command to read the led state out of the keyboard.
>
You can query the state of the keyboard according to BIOS by looking in
byte 0x417 absolute, or by issuing int 0x16, ah = 0x02 (or ah = 0x12)
from real mode.
-hpa
prev parent reply other threads:[~2007-02-15 14:19 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
2007-02-18 17:54 ` Randy Dunlap
2007-02-14 19:26 ` Arjan van de Ven
2007-02-15 14:25 ` H. Peter Anvin [this message]
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=45D46D3C.3010407@zytor.com \
--to=hpa@zytor.com \
--cc=dax@gurulabs.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).