Here is the patch.
I'll send it to linux-acpi soon, but it's already in the acpi4asus git tree.
** Attachment added: "Fix keycodes"
http://launchpadlibrarian.net/25964112/0006-asus-laptop-fix-input-keycode.patch
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Chang
I've made a few tests. With 2.6.30 rc2 I get the same results as 2.6.29.
The problem of events sent twice is not really hard to solve: these events are
sent both by the kernel module (acpi_laptop) and by acpi_fakekey. But if I
understood correctly, acpi_fakekey is deprecated? So this should be so
Thanks for your answer.
I have tested 2.6.29-1 kernel: it's a better but there are still 2 issues:
First, there are 2 keys with an input event >255 (0x0ff):
-"hotkey ATKD 005c " mapped to BTN_EXTRA (0x179). I think it should
be mapped to KEY_SCREENLOCK instead as this is what this but
Hi Sika,
Unfortunately the kernel is currently frozen for the upcoming Jaunty
9.04 release. Any fixes will likely have to wait for Karmic. I'm also
unsure of the likelyhood that this would qualify for a Stable Release
Update to Jaunty - http://wiki.ubuntu.com/StableReleaseUpdates.
However, I wou
Looking at asus-laptop module code in 2.6.29
(http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.29.y.git;a=blob;f=drivers/platform/x86
/asus-
laptop.c;h=eeafc6c0160dbe41b827a627f77c842d396adbd6;hb=8d7bff2d72660d9d60aa371ae3d1356bbf329a09)
it seems like it is solved in 2.6.29 (I didn't test
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/25482839/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/25482840/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/25482842/Dependencies.txt
** A
