| 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: Wed, 13 Nov 2013 11:47:18 +0100 (CET) From: Jiri Kosina <jkosina@...e.cz> To: Pali Rohár <pali.rohar@...il.com> Cc: linux-kernel@...r.kernel.org, linux-input@...r.kernel.org, Dmitry Torokhov <dmitry.torokhov@...il.com> Subject: Re: input question: ambient light sensor button On Sun, 15 Sep 2013, Pali Rohár wrote: > I do not know where to ask this question, but I think that kernel > developers could help me. > > I have notebook with one special button on keyboard which is > designed for turning ambient light sensor on and off. By default > pressing button do nothing (I can turn ambient light sensor on/off > via sysfs platform wmi module). Button press is reported by > kernel input device AT Translated Set 2 keyboard and reports it > as button "touchpad off". > > Of course "touchpad off" is incorrect and I'd like to ask which > kernel key or button from /usr/include/linux/input.h should be > mapped for my ambient light sensor button? Is there already some? > And what is strategy for allocating KEY_* and BTN_* numbers? This is maintained by Dmitry, so he's the one to answer this. I am adding him to CC. > I'd like to know this, so udev could have correct DMI keymap > hooks and other userspace programs can understand ambient light > sensor button correctly. -- Jiri Kosina SUSE Labs -- 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