| 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
| ||
|
Date: Mon, 14 Jan 2008 10:27:06 +0000 From: Samuel Thibault <samuel.thibault@...-lyon.org> To: "H. Peter Anvin" <hpa@...or.com> Cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] Default keyboard LEDs H. Peter Anvin, le Sun 13 Jan 2008 19:50:34 -0800, a écrit : > >Actually, what would be perfect would be to use the configuration that > >the BIOS sets at boot by default. That is device-dependent, however. > > > > It is, but it can be read out either by INT calls at initialization > time, or by reading out the byte at physical address 0x417: I should have said "arch-dependent". I didn't mean it wasn't possible, but just it'd probably be better that driver experts do it, not me :) > --------K-M00400017-------------------------- > MEM 0040h:0017h - KEYBOARD - STATUS FLAGS 1 > Size: BYTE > SeeAlso: MEM 0040h:0018h,INT 16/AH=02h,MEM 0040h:0096h > > Bitfields for keyboard status flags 1: > Bit(s) Description (Table M0010) > 7 INSert active > 6 Caps Lock active > 5 Num Lock active > 4 Scroll Lock active > 3 either Alt pressed > 2 either Ctrl pressed > 1 Left Shift pressed > 0 Right Shift pressed > SeeAlso: #M0011,#00587 > > The same information is available through INT 16h, AH=02h. Samuel -- 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