thinkpad_acpi does send scancodes, but only when it's reporting
KEY_UNKNOWN, and then it sends the scancode after the keycode. keymap
seems to expect that there's always a scancode and that it will always
come before the keycode. Do you know if there's any requirement to send
the scancode or for the order of the events? I do see a number of
drivers that don't send scancodes, but of those that do all that I
looked at except thinkpad_acpi send the scancode before the keycode.

Maybe keymap needs to wait for the sync event before printing make sure
it receives both events?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702407

Title:
  thinkpad_acpi generated EV_KEY events are mssing scancodes

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to