public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Use BIOS Keyboard variable to set Numlock
Date: Wed, 11 Jul 2007 17:58:39 -0700	[thread overview]
Message-ID: <46957CBF.1000101@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0707112305390.2432@be1.lrz>

Bodo Eggert wrote:
> 
> Instead of the byte at 0x497 as suggested in that thread, I'm using the 
> byte at 0x417, which reflects the intended LED state. In order to change 
> the keyboard LED, DOS programs would change this byte and call INT 5
> (which is the keyboard software interrupt).
> 

0x417 is actually the current keyboard modifier state, which is the
right thing to use.

Presumably you meant INT 9 (IRQ 1), not INT 5 which is the print screen
interrupt (also used by the CPU for BOUND error, which has some amusing
consequence if anyone ever used the BOUND instruction in DOS.)

That being said, one could argue that since this is a BIOS interface it
should be queried via INT 16h, AH=02h and stuffed in the zeropage
structure.  This would also solve the issue of it not being supported by
non-BIOS firmware.

	-hpa

  reply	other threads:[~2007-07-12  0:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 22:13 [PATCH] Use BIOS Keyboard variable to set Numlock Bodo Eggert
2007-07-12  0:58 ` H. Peter Anvin [this message]
2007-07-12  1:41   ` Bodo Eggert
2007-07-12  2:10     ` H. Peter Anvin
2007-07-13 18:25       ` Bodo Eggert
  -- strict thread matches above, loose matches on Subject: below --
2012-02-26 20:05 Joshua C.

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=46957CBF.1000101@zytor.com \
    --to=hpa@zytor.com \
    --cc=7eggert@gmx.de \
    --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