<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Cannot remap keys of bluetooth keyboard" href="https://bugs.freedesktop.org/show_bug.cgi?id=82482#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Cannot remap keys of bluetooth keyboard" href="https://bugs.freedesktop.org/show_bug.cgi?id=82482">bug 82482</a> from <a class="email" href="mailto:jm@lentin.co.uk" title="Jamie Lentin <jm@lentin.co.uk>"> Jamie Lentin</a> <pre>Before with /lib/udev/keymap it was pretty easy to write a custom udev rule to apply a keymap: SUBSYSTEM=="input", \ ATTRS{name}=="ThinkPad Compact Bluetooth Keyboard with TrackPoint", \ RUN+="keymap $name /etc/udev/keymaps/thinkpad-bluetooth-keyboard.map" ...so I wouldn't have noticed that the default rules don't play around with bluetooth keyboards. NB: my remappings themselves are not worthy of upstream, just my own odd quirks. Now with hwdb I have 2 levels of indirection to mine through. I presume adding my own rule (and associated hwdb entry) like this would work: SUBSYSTEM=="input", \ ATTRS{name}=="ThinkPad Compact Bluetooth Keyboard with TrackPoint", \ IMPORT{builtin}="hwdb 'keyboard:custom:compact-bluetooth-keyboard'", \ RUN{builtin}+="keyboard" However, adding this udev rule and inventing my own namespace seems unnecessary. A hwdb mapping for bluetooth devices, or bluetooth devices using using the "keyboard:name:" mapping would mean I just have to add entries to hwdb, as with other keyboard types. Unfortunately I am currently away, however will suggest a patch next week.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>