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 solved in karmic: we'll only have to remove some stuff from acpi-support package (files in /etc/acpi and /etc/acpi/events).
Now the only thing that needs to be done in the kernel is replacing 3 keycodes in asus-laptop.c:
l272, "{KE_KEY, 0x43, KEY_STOP}," should be replaced by "{KE_KEY, 0x43, KEY_STOPCD},"
l276, "{KE_KEY, 0x5C, BTN_EXTRA}," should be replaced by "{KE_KEY, 0x5C, KEY_SCREENLOCK},"
l281, "{KE_KEY, 0x8A, KEY_TV}," should be replaced by "{KE_KEY, 0x8A, KEY_PROG1},"
So can anyone send this patch upstream before the 2.6.30 release? Or tell me how to do it.
Thanks
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 solved in karmic: we'll only have to remove some stuff from acpi-support package (files in /etc/acpi and /etc/acpi/events).
Now the only thing that needs to be done in the kernel is replacing 3 keycodes in asus-laptop.c:
l272, "{KE_KEY, 0x43, KEY_STOP}," should be replaced by "{KE_KEY, 0x43, KEY_STOPCD},"
l276, "{KE_KEY, 0x5C, BTN_EXTRA}," should be replaced by "{KE_KEY, 0x5C, KEY_SCREENLOCK},"
l281, "{KE_KEY, 0x8A, KEY_TV}," should be replaced by "{KE_KEY, 0x8A, KEY_PROG1},"
So can anyone send this patch upstream before the 2.6.30 release? Or tell me how to do it.
Thanks