linux-kernel - Re: Linus' laptop and Num lock status

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] [day] [month] [year] [list]

Date:	Tue, 20 Feb 2007 14:57:01 +0100
From:	Helge Hafting <helge.hafting@...el.hist.no>
To:	Krzysztof Halasa <khc@...waw.pl>
CC:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Dax Kelson <dax@...ulabs.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jean Delvare <khali@...ux-fr.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Linus' laptop and Num lock status

Krzysztof Halasa wrote:
> Jan Engelhardt <jengelh@...ux01.gwdg.de> writes:
>
>   
>>> I checked, and looking at offset 0x497 seems to work fine on a couple of
>>> systems with USB keyboards.
>>>       
>> Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
>> return when there is actually more than one USB keyboard connected at boot.
>>     
>
> I bet all would share LED states. If you can use multiple keyboards
> in legacy mode at all, of course.
>   
I have used multiple keyboards, for a 2-user machine.

The bios interact with only one of the keyboards, and track LED state on 
that.
Other keyboard(s) become useful once the linux comes up with
its event interface. You then have one set of LEDS per keyboard.

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