lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 11 Jul 2007 17:58:39 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Bodo Eggert <7eggert@....de>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] Use BIOS Keyboard variable to set Numlock

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists