[systemd-devel] update: udev keymaps are moving to hwdb
kay at vrfy.org
Wed Jul 10 14:38:12 PDT 2013
We need to cut down the use of udev rules, and move all hardware
matches to the magnitudes more efficient hardware database. Udev rules
were not meant to carry out huge lists of sequential matches against
hardware IDs, this model just doesn't scale too well.
The keymaps are the first, other users like libsane, libgphoto, media
player, ... should be converted too.
The systemd git source tree has now all the pieces to prepare the move
from the current keymap handling to the hardware database. None of it
will take any action at the moment, the hwdb file is not committed.
All keymap scan/key code pairs, and the force-release lists will move
into the file:
The input device will import the keymap data into the udev database like:
$ udevadm test /class/input/event5
There is a new builtin "keyboard" which will read these keys and
install them into the kernel device.
The force-release flag is carried as '!' in front of the key identifier like:
After all keymap data is moved to the 60-keyboard.hwdb file, all
current keymap files, force-release files, the keymap binary, the udev
rule and the force-release shell script will be removed from the
Attached is the current version of the hwdb file, which is not
committed to the source tree. It contains maybe 30% of the old keymaps
and should cover all of the force-release lists. The header of the
file carries some documentation.
Some data like USB devices with too broad and insufficient matches on
the USB strings instead of the USB IDs cannot be ported over and need
to be reworked if they are still needed.
Any help or testing would be more than welcome to get that thing
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 20193 bytes
Desc: not available
More information about the systemd-devel