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-next>] [day] [month] [year] [list]
Date:	Sun, 15 Sep 2013 15:53:33 +0200
From:	Pali Rohár <pali.rohar@...il.com>
To:	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: input question: ambient light sensor button

Hello,

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?

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.

-- 
Pali Rohár
pali.rohar@...il.com

Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ