[Pkg-acpi-devel] Bug#521280: how to make acpid react to hotkeys now?

[Henrique de Moraes Holschuh]

On Wed, 15 Apr 2009, martin f krafft wrote:
> I've read all of the documentation on thinkpad-acpi and I think
> I understand it; I also understand what it's trying to do and
> acknowledge that it is progress.
> 
> However, no matter how hard I try, I cannot figure out how to make
> my system react to Fn-FX keypresses on the Thinkpad X40.
> 
> I used to have Fn-F1 and Fn-F2 in use, and while the latter
> generates an X event that gets translated into 0x0 "NoSymbol",
> I cannot get any reaction (neither input nor netlink) from Fn-F1,
> even after

You can use a HAL .fdi file to set a X-friendly keycode for the
thinkpad-acpi scan map positions 0x00 (fn+f1), 0x01 (fn+f2).

You can also use input-kbd from the input-tools package (but that thing
really reeks of a half-assed debug interface, since it can't even do proper
matching of input devices so you have to do a lot of shell dance to find out
the input device number you need from lsinput, first).

These ARE mapped to something by default, but probably X evdev still can't
handle keycodes above 255 (I understand the fix for that is more like
genetic therapy on the X server and protocols, than a brain surgery).

> How am I supposed to react to these events nowadays?

Well, the very best would be to improve the hal input event helper to make
it grow generic "hey, do this configurable thing when you get this
configurable input event" functionality, then use that.  I don't have time
to tack that in the near future :-(

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh