systemd/rules/60-keyboard.rules

# do not edit this file, it will be overwritten on update

ACTION=="remove", GOTO="keyboard_end"
KERNEL!="event*", GOTO="keyboard_end"
ENV{ID_INPUT_KEY}=="", GOTO="keyboard_end"

# skip later rules when we find something for this input device
IMPORT{builtin}="hwdb --lookup-prefix=keyboard:", \
  RUN{builtin}+="keyboard", GOTO="keyboard_end"

# import key mapping for AT keyboard from DMI data
DRIVERS=="atkbd", IMPORT{builtin}="hwdb 'keyboard:$attr{[dmi/id]modalias}'", \
  RUN{builtin}+="keyboard", GOTO="keyboard_end"

# lookup entries matching the machine's DMI data
IMPORT{builtin}="hwdb 'keyboard:name:$attr{name}:$attr{[dmi/id]modalias}'", \
  RUN{builtin}+="keyboard", GOTO="keyboard_end"

LABEL="keyboard_end"
udev: add builtin 'keyboard' to manage key mappings 2013-07-10 18:02:24 +04:00			`# do not edit this file, it will be overwritten on update`

udev: keyboard - also hook into "change" events Re-apply the keymaps when "udevadm trigger" is called. Hooking into "add" only would just remove all keymap content from the udev database instead of applying the new config. 2014-05-26 05:30:21 +04:00			`ACTION=="remove", GOTO="keyboard_end"`
udev: add builtin 'keyboard' to manage key mappings 2013-07-10 18:02:24 +04:00			`KERNEL!="event*", GOTO="keyboard_end"`
			`ENV{ID_INPUT_KEY}=="", GOTO="keyboard_end"`

rules: keyboard - remove "platform" from comments 2015-03-16 15:43:50 +03:00			`# skip later rules when we find something for this input device`
hwdb: convert to generic input-modalias matches There is no reason to match on usb-modaliases, if we can use the input-modalias to achieve the same. This commit changes the keyboard-lookups to not be restricted to USB, but pass all modaliases to the hwdb. Furthermore, we convert all usb:* matches to input:* matches, thus getting rid of any ambiguity if multiple usb devices are chained (or a bluetooth device / etc. is on top). Note that legacy keyboard:usb:* matches are still supported, but deprecated. If possible, please use keyboard:input:* matches instead. This is a required step to make other input devices work with 60-keyboard.hwdb. Other bus-types are often chained on usb and we want to avoid any ambiguity here if we incorrectly match on a USB hub. 2015-03-16 14:00:46 +03:00			`IMPORT{builtin}="hwdb --lookup-prefix=keyboard:", \`
rules: keyboard - use builtin command 2013-07-18 16:40:42 +04:00			`RUN{builtin}+="keyboard", GOTO="keyboard_end"`
udev: add builtin 'keyboard' to manage key mappings 2013-07-10 18:02:24 +04:00
Revert "hwdb: merge atkbd into platform matches" This reverts commit ba76ee29bc02879fb42c048132af8889b00220d5. As it turns out, we need to match on driver=atkbd to not load the fixups on any plugged USB devices. That is, whenever you use "name:<name>:dmi:<dmi>" style matches, you better provide a name or you're screwing things up. 2015-03-16 17:51:25 +03:00			`# import key mapping for AT keyboard from DMI data`
			`DRIVERS=="atkbd", IMPORT{builtin}="hwdb 'keyboard:$attr{[dmi/id]modalias}'", \`
			`RUN{builtin}+="keyboard", GOTO="keyboard_end"`

rules: keyboard - remove "platform" from comments 2015-03-16 15:43:50 +03:00			`# lookup entries matching the machine's DMI data`
rules: drop redundant match The 60-keyboard rules are already guared by KERNEL!="event" bail-outs, therefore, KERNELS="input" is always true. Drop it! 2015-03-16 14:05:36 +03:00			`IMPORT{builtin}="hwdb 'keyboard:name:$attr{name}:$attr{[dmi/id]modalias}'", \`
rules: keyboard - use builtin command 2013-07-18 16:40:42 +04:00			`RUN{builtin}+="keyboard", GOTO="keyboard_end"`
udev: add builtin 'keyboard' to manage key mappings 2013-07-10 18:02:24 +04:00
			`LABEL="keyboard_end"`