I hacked atkbd.c to dump every keycode and enabled CONFIG_EVBUG yet
the Fn+F{1..12} and Fn+{arrow} keys don't register an event. Is there
a way to hack the ACPI drivers to dump keycodes?
>From hacking at the Windows drivers, pressing the hotkeys generates an
acpi event. How do I get the acpi key events dumped?
One-liners if possible, please.
--
Andrey Vul
On Mon, 17 Nov 2008, Andrey Vul wrote:
> I hacked atkbd.c to dump every keycode and enabled CONFIG_EVBUG yet
> the Fn+F{1..12} and Fn+{arrow} keys don't register an event. Is there
> a way to hack the ACPI drivers to dump keycodes?
>
> From hacking at the Windows drivers, pressing the hotkeys generates an
> acpi event. How do I get the acpi key events dumped?
Shouldn't just running 'acpidump' be sufficient for you?
--
Jiri Kosina
SUSE Labs
On Mon, Nov 17, 2008 at 08:36:02PM -0500, Andrey Vul wrote:
> I hacked atkbd.c to dump every keycode and enabled CONFIG_EVBUG yet
> the Fn+F{1..12} and Fn+{arrow} keys don't register an event. Is there
> a way to hack the ACPI drivers to dump keycodes?
>
> From hacking at the Windows drivers, pressing the hotkeys generates an
> acpi event. How do I get the acpi key events dumped?
If there's a driver for your machine, acpidump or just watch
/proc/acpi/events (and then port the driver to create an input device
and use that instead). If there's no existing driver, you get to write
one. There's no standard spec for sending hotkeys over ACPI, other than
sleep, power and lid.
--
Matthew Garrett | [email protected]