[systemd-bugs] [Bug 78408] USB and DMI keyboard mappings behave differently

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=78408

--- Comment #6 from David Herrmann <dh.herrmann at gmail.com> ---
Can you please describe what you mean by "it's not working"? And please be as
specific as possible.

Your evtest-log on stackexchange.com shows that the remapping worked
_perfectly_. So please let us know what exactly is going wrong.

Btw., you're _highly_ advised to _not_ mess with scancode-mappings except for
faulty hardware. What you want, is a custom keymap, not a custom scanmap.
Therefore, you should modify your XKB keymaps, not the kernel scanmaps.
Why, you ask? Because multiple scancodes mapping to the same keycode does not
yield the same result as one would expect. The state tracking is still only one
bit and done on the _keycode_, not on the _scancode_. This does not happen if
you write proper XKB keymaps, which can deal with all that.

Btw., there is no difference between modifiers and non-modifiers on the kernel
level (or keycode level, or scancode level). The "modifier" concept is
introduced by keymaps that XKB provides.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140602/37be0b4a/attachment.html>