[systemd-bugs] [Bug 82311] New: /lib/udev/hwdb.d/60-keyboard.hwdb documentation issues

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 82311
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: /lib/udev/hwdb.d/60-keyboard.hwdb documentation issues
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: minor
    Classification: Unclassified
                OS: All
          Reporter: vincent-fdt at vinc17.net
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

This is a copy of my bug report in the Debian BTS:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757367
(for systemd/208-7).

/lib/udev/hwdb.d/60-keyboard.hwdb contains some documentation at the beginning,
but there are several problems with it.

First, a typo: charcter -> character

It says:

#  Scan codes are specified as:
#    KEYBOARD_KEY_<hex scan code>=<key code identifier>
#  The scan code should be expressed in hex lowercase and in
#  full bytes, a multiple of 2 digits. The key codes are retrieved
               ^^^^^^^^^^^^^^^^^^^^^^
#  and normalized from the kernel input API header.

but in the settings, scan codes are also expressed on 3 or 5 digits, e.g.

# enhanced USB keyboard
keyboard:usb:v04B3p301B*
 KEYBOARD_KEY_90001=prog1 # ThinkVantage
 KEYBOARD_KEY_90002=screenlock
 KEYBOARD_KEY_90003=file
 KEYBOARD_KEY_90004=wordprocessor
 KEYBOARD_KEY_90005=spreadsheet
 KEYBOARD_KEY_90006=calc
 KEYBOARD_KEY_90007=mail
 KEYBOARD_KEY_90008=www

# Satellite U940
keyboard:name:Toshiba*input*device:dmi:bvn*:bvr*:bd*:svnTOSHIBA*:pnSATELLITEU940:pvr*
 KEYBOARD_KEY_13c=brightnessdown
 KEYBOARD_KEY_13d=brightnessup
 KEYBOARD_KEY_13e=switchvideomode
 KEYBOARD_KEY_13f=f21                                   # Touchpad toggle

Thus this is confusing.

It also says:

# To debug key presses and access scan code mapping data of
# an input device use the commonly available tool: evtest(1).

Unfortunately, evtest doesn't output scan codes for some keys:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757356

The udev keymap utility had the same problem, but once patched, it could output
the full keymap as a workaround. Unfortunately, evtest cannot do that (well, I
didn't see anything like that in its documentation). The input-kbd utility can
do that, so that it would be a good idea to mention it too.

Moreover this file should also say how one can do some tests and where one can
look for error messages.

And what should be done to take the changes into account? After a search on the
web, it seems that most users don't know either.

http://marcin.juszkiewicz.com.pl/2014/03/03/how-to-get-zoom-slider-on-microsoft-keyboard-recognized-by-x11/

says:

  udevadm hwdb --update
  udevadm control --reload

but one needs to replug the keyboard (or reboot!).

http://askubuntu.com/questions/499252/my-custom-udev-hwdb-rule-doesnt-work

just says:

  udevadm hwdb --update

but it doesn't work.

http://forums.fedoraforum.org/showpost.php?p=1681790&postcount=3

says:

  udevadm hwdb --update
  udevadm trigger
  udevadm control --reload

which might be the solution.

-- 
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/20140807/094bf7bb/attachment.html>