linux-kernel - Re: [PATCH] Use BIOS Keyboard variable to set Numlock

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]

Message-ID: <46958D9D.9090802@zytor.com>
Date:	Wed, 11 Jul 2007 19:10:37 -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:
> 
>> 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.
> 
> This is an interesting option, but it's more invasive. I'd rather like a 
> feedback saying we can depend on that data area to be there.

I don't think we can.  You might find garbage there.

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