mirrors/systemd
0
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-27 04:03:36 +08:00
Code Issues Packages Projects Releases Wiki Activity
b4dfe06e19
systemd/hwdb.d/60-keyboard.hwdb

1853 lines
78 KiB
Plaintext
Raw Normal View History

hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
# This file is part of systemd.
#
hwdb: Add new quirk type to documentation Missed in b698b5c.
2017-03-09 23:40:25 +08:00
# This file contains 3 types of metadata to apply to keyboards and
hwdb: Better documentation for keyboard quirks Split up the device matching explanation, and add documentation for the fixed layout quirk.
2017-03-09 21:47:53 +08:00
# keyboard-like input devices:
# - Key mapping
# - Hard-coded layouts
hwdb: Add new quirk type to documentation Missed in b698b5c.
2017-03-09 23:40:25 +08:00
# - Absence of modifier LEDs
hwdb: Better documentation for keyboard quirks Split up the device matching explanation, and add documentation for the fixed layout quirk.
2017-03-09 21:47:53 +08:00
#
# The matching process is the same for the different types of metadata.
#
# ########################### MATCHING #######################################
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
#
# The lookup keys are composed in:
hwdb: fix comment referring to rules file 60-keyboard.rules was renamed to 60-evdev.rules in 51c0c2869 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-11-22 12:54:06 +08:00
# 60-evdev.rules
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
#
hwdb: reindent commments and say that "*" should always be trailing
2020-10-15 15:22:35 +08:00
# Note: The format of the "evdev:" prefix match key is a contract between the
# rules file and the hardware data, it might change in later revisions to
# support more or better matches, it is not necessarily expected to be a stable
# ABI.
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
#
# Supported hardware matches are:
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 19:00:46 +08:00
# - Generic input devices match:
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
# evdev:input:bZZZZvYYYYpXXXXeWWWW-VVVV
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 19:00:46 +08:00
# This matches on the kernel modalias of the input-device, mainly:
# ZZZZ is the bus-id (see /usr/include/linux/input.h BUS_*), YYYY, XXXX and
hwdb: Correct WWWW Pattern In Documentation Comment
2019-10-02 08:42:58 +08:00
# WWWW are the 4-digit hex uppercase vendor, product and version ID and VVVV
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 19:00:46 +08:00
# is an arbitrary length input-modalias describing the device capabilities.
hwdb: clarify where to find the modalias and vid/pid information (#4952) Fixes #4938
2016-12-22 17:20:02 +08:00
# The vendor, product and version ID for a device node "eventX" is listed
# in /sys/class/input/eventX/device/id.
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08: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 22:51:25 +08:00
# - AT keyboard DMI data matches:
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
# evdev:atkbd:dmi:bvn*:bvr*:bd*:svn<vendor>:pn<product>:pvr*
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 22:51:25 +08:00
# <vendor> and <product> are the firmware-provided strings
hwdb: clarify where to find the modalias and vid/pid information (#4952) Fixes #4938
2016-12-22 17:20:02 +08:00
# exported by the kernel DMI modalias, see /sys/class/dmi/id/modalias
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 22:51:25 +08:00
#
hwdb: merge atkbd into platform matches Currently, we always run hwdb 'keyboard:name:$attr{name}:$attr{[dmi/id]modalias}' as last step to match keyboards. Therefore, if nothing else matched so far, we still try the device-name+dmi combination. However, we have a special atkbd rule which is only run for atkbd as: hwdb 'keyboard:$attr{[dmi/id]modalias}' This is redundant, as we already pass the same information to hwdb in the last fallback step. This patch converts the hwdb "keyboard:dmi:*" matches to "keyboard:name:*:dmi:*" matches and drops the redundant rule.
2015-03-16 19:19:09 +08:00
# - Input driver device name and DMI data match:
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
# evdev:name:<input device name>:dmi:bvn*:bvr*:bd*:svn<vendor>:pn*
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 22:51:25 +08:00
# <input device name> is the name device specified by the
# driver, <vendor> is the firmware-provided string exported
hwdb: clarify where to find the modalias and vid/pid information (#4952) Fixes #4938
2016-12-22 17:20:02 +08:00
# by the kernel DMI modalias, see /sys/class/dmi/id/modalias
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
#
rules: Add extended evdev/input match rules for event nodes with the same name Sometimes a system may have 2 input event nodes with the same name where we only want to apply keyboard hwdb rules to 1 of the 2 devices. This problem happens e.g. on devices where the soc_button_array driver is used (e.g. intel atom based tablets) which registers 2 event nodes with the name "gpio-keys". This commit adds a new extended match rule which extends the match to also check $attr{phys} and $attr{capabilities/ev}, allowing to differentiate between devices with an identical name. Suggested-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2017-02-12 19:33:22 +08:00
# - Extended input driver device name, properties and DMI data match:
# evdev:name:<input device name>:phys:<phys>:ev:<ev>:dmi:bvn*:bvr*:bd*:svn<vendor>:pn*
# <input device name> is the name device specified by the
# driver, <phys> is the physical-device-path, "cat
# /sys/class/input/input?/phys", <ev> is the event bitmask, "cat
# /sys/class/input/input?/capabilities/ev" and <vendor> is the
# firmware-provided string exported by the kernel DMI modalias,
# see /sys/class/dmi/id/modalias
hwdb: reindent commments and say that "*" should always be trailing
2020-10-15 15:22:35 +08:00
#
# All matches should end in ':*' to allow future expansions of the match key.
hwdb: Better documentation for keyboard quirks Split up the device matching explanation, and add documentation for the fixed layout quirk.
2017-03-09 21:47:53 +08:00
# ######################### KEY MAPPING ######################################
#
# Keyboard mapping of scan codes to key codes, and
# scan codes to add to the AT keyboard's 'force-release' list.
rules: Add extended evdev/input match rules for event nodes with the same name Sometimes a system may have 2 input event nodes with the same name where we only want to apply keyboard hwdb rules to 1 of the 2 devices. This problem happens e.g. on devices where the soc_button_array driver is used (e.g. intel atom based tablets) which registers 2 event nodes with the name "gpio-keys". This commit adds a new extended match rule which extends the match to also check $attr{phys} and $attr{capabilities/ev}, allowing to differentiate between devices with an identical name. Suggested-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2017-02-12 19:33:22 +08:00
#
hwdb: update format description and document reloading https://bugs.freedesktop.org/show_bug.cgi?id=82311
2014-08-08 09:48:57 +08:00
# Scan codes are specified as:
# KEYBOARD_KEY_<hex scan code>=<key code identifier>
# The scan code should be expressed in hex lowercase. The key codes
# are retrieved and normalized from the kernel input API header.
hwdb: support pressing buttons on a keyboard Support BTN_* codes with btn_ prefix and keys with KEY_ prefix optionally removed.
2017-06-07 21:28:18 +08:00
# Keycodes are either KEY_* defines in lowercase with the key_ prefix
# optionally removed or BTN_ defines in lowercase with btn_ preserved.
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
#
hwdb: update format description and document reloading https://bugs.freedesktop.org/show_bug.cgi?id=82311
2014-08-08 09:48:57 +08:00
# An '!' as the first character of the key identifier string
# will add the scan code to the AT keyboard's list of scan codes
# where the driver will synthesize a release event and not expect
# it to be generated by the hardware.
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
#
# To debug key presses and access scan code mapping data of
# an input device use the commonly available tool: evtest(1).
hwdb: add XKB_FIXED_LAYOUT/VARIANT to the keyboard hwdb Yubikeys and other pseudo keyboards require that they are in the US layout, otherwise the data they send is invalid. Add two new keys to signal this to processes that handles (XKB) layouts.
2016-11-22 13:21:24 +08:00
# A device with a fixed keyboard layout that must not be changed by
# the desktop environment may specify that layout as:
# XKB_FIXED_LAYOUT="us"
# XKB_FIXED_VARIANT=""
# Examples of such devices: the Yubikey or other key-code generating
# devices.
hwdb: add XKB_FIXED_MODEL to the keyboard hwdb Chromebook keyboards have a top row which generates f1-f10 key codes but the keys have media symbols printed on them. A simple scan code to key code mapping to the correct media keys makes the f1-f10 inaccessible. To properly use the keyboard a custom key code to symbol mapping in xbk is required (a variant of the chromebook xkb model is already upstream). Other devices have similar problems. This commit makes it possible to specify which xkb model should be used for a specific device by setting XKB_FIXED_MODEL.
2019-10-31 21:27:24 +08:00
# A device where the scan code to key code mapping is insufficient and
# requires a special key code to symbol configuration may specify that with:
# XKB_FIXED_MODEL="xkbmodel"
# Examples of such devices: Chromebooks where the top row is used for both
# media and F1-F10 keys.
hwdb: update format description and document reloading https://bugs.freedesktop.org/show_bug.cgi?id=82311
2014-08-08 09:48:57 +08:00
# To update this file, create a new file
hwdb: fix a typo
2014-11-25 18:45:50 +08:00
# /etc/udev/hwdb.d/70-keyboard.hwdb
hwdb: update format description and document reloading https://bugs.freedesktop.org/show_bug.cgi?id=82311
2014-08-08 09:48:57 +08:00
# and add your rules there. To load the new rules execute (as root):
hwdb: use systemd-hwdb instead of obsolete udevadm hwdb (#4722) Fixes: #4721
2016-11-24 02:21:56 +08:00
# systemd-hwdb update
hwdb: update format description and document reloading https://bugs.freedesktop.org/show_bug.cgi?id=82311
2014-08-08 09:48:57 +08:00
# udevadm trigger /dev/input/eventXX
# where /dev/input/eventXX is the keyboard in question. If in
hwdb: fix help text in 60-keyboard.hwdb udevadm trigger /dev/input/event* does not work use udevadm trigger --verbose --sysname-match="event*"
2017-06-08 01:26:25 +08:00
# doubt, simply reload all input rules
# udevadm trigger --verbose --sysname-match="event*"
hwdb: update format description and document reloading https://bugs.freedesktop.org/show_bug.cgi?id=82311
2014-08-08 09:48:57 +08:00
#
Update bugtracker address
2015-08-04 12:03:55 +08:00
# If your changes are generally applicable, preferably send them as a pull
# request to
# https://github.com/systemd/systemd
# or create a bug report on https://github.com/systemd/systemd/issues and
# include your new rules, a description of the device, and the output of
hwdb: remove references to udevadm info /dev/input/event*
2015-12-25 02:34:24 +08:00
# udevadm info /dev/input/eventXX.
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
##########################################
# Acer
##########################################
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.
2013-12-19 15:33:32 +08:00
# common keys
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*
Revert "hwdb: Apply Acer mappings to all Gateway and Packard Bell models" This reverts commit e09dba97b96f877e36cd3f1afdb321922eed064b. It's reported that the same rules for Acer cause false match and unexpected response from certain keys on an old PackardBell laptop. Bug: https://github.com/systemd/systemd/issues/12178
2019-05-02 17:46:45 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr*
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svneMachines:pneMachines*E725:pvr*
hwdb: Fix airplane mode key for all Acer series According to the key code v2.02 from Acer, scancode E0 86 will be generated for airplane mode hotkey. Verified on Aspire, TravelMate, Easynote and Predator.
2017-04-12 21:03:35 +08:00
KEYBOARD_KEY_86=wlan # Fn+F3 or Fn+Q for comunication key
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_a5=help # Fn+F1
KEYBOARD_KEY_a6=setup # Fn+F2 Acer eSettings
KEYBOARD_KEY_a7=battery # Fn+F3 Power Management
KEYBOARD_KEY_a9=switchvideomode # Fn+F5
keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.
2013-12-19 15:33:32 +08:00
KEYBOARD_KEY_b2=www
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_b3=euro
KEYBOARD_KEY_b4=dollar
KEYBOARD_KEY_ce=brightnessup # Fn+Right
KEYBOARD_KEY_d4=bluetooth # (toggle) off-to-on
KEYBOARD_KEY_d5=wlan # (toggle) on-to-off
KEYBOARD_KEY_d6=wlan # (toggle) off-to-on
KEYBOARD_KEY_d7=bluetooth # (toggle) on-to-off
KEYBOARD_KEY_d8=bluetooth # (toggle) off-to-on
KEYBOARD_KEY_d9=brightnessup # Fn+Right
KEYBOARD_KEY_ee=brightnessup # Fn+Right
KEYBOARD_KEY_ef=brightnessdown # Fn+Left
KEYBOARD_KEY_f1=f22 # Fn+F7 Touchpad toggle (off-to-on)
KEYBOARD_KEY_f2=f23 # Fn+F7 Touchpad toggle (on-to-off)
KEYBOARD_KEY_f3=prog2 # "P2" programmable button
KEYBOARD_KEY_f4=prog1 # "P1" programmable button
KEYBOARD_KEY_f5=presentation
hwdb: Add power button mapping for Acer models The power key keycode e076 is emitted on several different Acer laptop models, and it is expected that it will also be used on upcoming models. Verified on the following models: Aspire ES1-421 Aspire ES1-432 Aspire A515-51 Aspire A515-51G Aspire A517-51 Aspire A517-51G Nitro AN515-31
2017-04-12 21:03:47 +08:00
KEYBOARD_KEY_f6=power # Power button
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_f8=fn
keymap: Fix wrong assignments to F23 These days, F21/F22/F23 mean Touchpad toggle/on/off. Clean up other assignments to that from ancient times which belong to keys like "Auto Brightness" (which doesn't have a keycode and is usually hardwired) or some "launch vendor tool" key. https://bugs.freedesktop.org/show_bug.cgi?id=62953
2013-09-20 05:42:10 +08:00
KEYBOARD_KEY_f9=prog1 # Launch NTI shadow
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
rules: keyboard - remove "platform" from comments
2015-03-16 20:43:50 +08:00
# Acer kernel driver
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Acer WMI hotkeys:dmi:bvn*:bvr*:bd*:svn*:pnAcer*:pvr*
replace tabs with spaces in some files Files: * hwdb/60-keyboard.hwdb * shell-completion/zsh/_systemd-coredumpctl * src/test/test-helper.h
2014-02-21 07:09:27 +08:00
KEYBOARD_KEY_82=f21 # Touchpad toggle
keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.
2013-12-19 15:33:32 +08:00
# Aspire models
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnAspire*:pvr*
keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.
2013-12-19 15:33:32 +08:00
KEYBOARD_KEY_84=bluetooth # sent when bluetooth module missing, and key pressed
KEYBOARD_KEY_d9=bluetooth # Bluetooth off
KEYBOARD_KEY_92=media # Acer arcade
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnAspire*5720*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnZG8*:pvr*
keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.
2013-12-19 15:33:32 +08:00
KEYBOARD_KEY_f4=prog3 # e-key
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnAspire*5920G:*
keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.
2013-12-19 15:33:32 +08:00
KEYBOARD_KEY_8a=media
KEYBOARD_KEY_a6=setup
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnAspire*6920:*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnAspire*8930:*
keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.
2013-12-19 15:33:32 +08:00
KEYBOARD_KEY_ca=prog3 # key 'HOLD' on CineDash Media Console
KEYBOARD_KEY_83=rewind
KEYBOARD_KEY_89=fastforward
KEYBOARD_KEY_9e=back
hwdb: release PageUp on Acer Aspire 7750G (#5476)
2017-02-28 03:55:43 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnAspire*7750G:pvr*
KEYBOARD_KEY_e0=!pageup
hwdb: Fix kbd brightness keys on Acer Predator PH 315-52 Acer defines Fn+F9/10 as keyboard brightness down/up on Predator PH 315-52 laptop. So, add the quirk to correct key mappings.
2020-04-09 16:20:36 +08:00
# Predator PH 315-52
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPredator*PH*315-52:pvr*
KEYBOARD_KEY_ef=kbdillumup # Fn+F10
KEYBOARD_KEY_f0=kbdillumdown # Fn+F9
keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.
2013-12-19 15:33:32 +08:00
# Travelmate C300
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnTravelMate*C3[01]0*:pvr*
keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.
2013-12-19 15:33:32 +08:00
KEYBOARD_KEY_67=f24 # FIXME: rotate screen
KEYBOARD_KEY_68=up
KEYBOARD_KEY_69=down
KEYBOARD_KEY_6b=fn
KEYBOARD_KEY_6c=screenlock # FIXME: lock tablet device/buttons
hwdb: Map 8a to f20 on the Acer Travelmate P648-G3-M This model emits 0x8a for the microphone-mute button above the keyboard, so let's map it to correct keycode. Signed-off-by: Chris Chiu <chiu@endlessm.com> Signed-off-by: João Paulo Rechi Vita <jprvita@endlessm.com>
2017-08-08 22:18:11 +08:00
# Travelmate P648-G2-MG, P648-G3-M and P645-S
hwdb: Map 0x8a to F20 on the Acer Travelmate P648-G2-MG This model emits 0x9a for the microphone mute button above the keyboard, so let's map it to correct keycode.
2017-04-04 22:48:06 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnTravelMate*P648-G2-MG*:pvr*
hwdb: Map 8a to f20 on the Acer Travelmate P648-G3-M This model emits 0x8a for the microphone-mute button above the keyboard, so let's map it to correct keycode. Signed-off-by: Chris Chiu <chiu@endlessm.com> Signed-off-by: João Paulo Rechi Vita <jprvita@endlessm.com>
2017-08-08 22:18:11 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnTravelMate*P648-G3-M*:pvr*
hwdb: fix mute microphone button on TravelMate P645-S (#8105)
2018-02-06 00:43:23 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnTravelMate*P645-S*:pvr*
hwdb: Map 0x8a to F20 on the Acer Travelmate P648-G2-MG This model emits 0x9a for the microphone mute button above the keyboard, so let's map it to correct keycode.
2017-04-04 22:48:06 +08:00
KEYBOARD_KEY_8a=f20 # Microphone mute button; should be micmute
keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.
2013-12-19 15:33:32 +08:00
# on some models this isn't brightnessup
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*5210*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*5220*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*5610*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*5620*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*5720*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnTravelMate*4720*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnTravelMate*6593:*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnAspire*1640:*
hwdb: keyboard - remove stray " <dvdhrm> kay, hwdb/60-keyboard.hwdb line 147 it says KEYBOARD_KEY_ee=screenlock" with a " at the end. I guess that's a typo?
2013-08-15 22:07:51 +08:00
KEYBOARD_KEY_ee=screenlock
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnAOA*:pvr*
keymap: Add release quirk for Acer AOA switchvideomode key https://launchpad.net/bugs/1272658
2014-01-29 01:10:12 +08:00
KEYBOARD_KEY_a9=!switchvideomode # Fn+F5
hwdb: Align airplane mode toggle key mapping for all Acer series Packard Bell and Gateway are different marketing names from Acer. The same scan code E0 86 is fired for the airplane mode toggle key. It was verified in commit d8d51328fe6db33a2d8cda06f181c55c00d09672. Signed-off-by: Chris Chiu <chiu@endlessm.com>
2019-05-02 18:10:22 +08:00
# Packard Bell and Gateway models
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pn*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnPackard*Bell*:pn*
Revert "hwdb: Apply Acer mappings to all Gateway and Packard Bell models" This reverts commit e09dba97b96f877e36cd3f1afdb321922eed064b. It's reported that the same rules for Acer cause false match and unexpected response from certain keys on an old PackardBell laptop. Bug: https://github.com/systemd/systemd/issues/12178
2019-05-02 17:46:45 +08:00
KEYBOARD_KEY_86=wlan # Fn+F3 or Fn+Q for comunication key
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# Alienware
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAlienware*:pn*
hwdb: Add support for Alienware touchpad toggle BugLink: https://bugs.launchpad.net/bugs/1605433
2019-03-07 00:28:10 +08:00
KEYBOARD_KEY_81=f21 # Touchpad toggle
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_8a=ejectcd
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: add support for Alienware graphics amplifier Unplugging and plugging in the cable will create various scancodes on the keyboard controller. Userspace within X should be able to interact with these to show interesting messages. Assign them to generic prog1/prog2. (David: add comment to hwdb explaining that these keycodes are reserved)
2015-06-11 11:01:51 +08:00
# Alienware/Dell reserves these keys; safe to apply on all their devices
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAlienware*:pn*:pvr*
KEYBOARD_KEY_bf=!prog1 #graphics amplifier, cable plug-in event
KEYBOARD_KEY_c1=!prog2 #graphics amplifier, undock-button event
KEYBOARD_KEY_c2=!power #graphics amplifier, surprise undock event
Alienware M17xR3 ejectcd button fix
2019-12-04 12:29:01 +08:00
# Alienware M17xR3 laptops
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAlienware*:pnM17xR3:*
KEYBOARD_KEY_89=ejectcd
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Asus
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnASUS:pn*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_ed=volumeup
KEYBOARD_KEY_ee=volumedown
KEYBOARD_KEY_ef=mute
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Asus WMI hotkeys:dmi:bvn*:bvr*:bd*:svnASUS*:pn*:pvr*
evdev:name:Eee PC WMI hotkeys:dmi:bvn*:bvr*:bd*:svnASUS*:pn*:pvr*
evdev:name:Asus Laptop extra buttons:dmi:bvn*:bvr*:bd*:svnASUS*:pn*:pvr*
replace tabs with spaces in some files Files: * hwdb/60-keyboard.hwdb * shell-completion/zsh/_systemd-coredumpctl * src/test/test-helper.h
2014-02-21 07:09:27 +08:00
KEYBOARD_KEY_6b=f21 # Touchpad Toggle
keymap: Add Asus WMI module We need to override the TOUCHPAD_TOGGLE to F21 to make it useful under X, as for other models.
2013-09-10 05:41:03 +08:00
hwdb: Fix micmute on ASUS FX503VD The micmute key needs to be remapped to F20 for userspace to consume it. See https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/121
2019-04-01 22:54:12 +08:00
# USB keyboard in Asus FX503VD
evdev:input:b0003v0B05p1869*
KEYBOARD_KEY_ff31007c=f20 # Remap micmute to f20
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# BenQ
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn*BenQ*:pn*Joybook*R22*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_6e=wlan
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: Add force-release for Clevo W65_67SZ media keys
2018-07-18 05:44:59 +08:00
###########################################################
# Clevo
###########################################################
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnNotebook:pnW65_67SZ:pvr*
KEYBOARD_KEY_a0=!mute
KEYBOARD_KEY_a2=!playpause
KEYBOARD_KEY_ae=!volumedown
KEYBOARD_KEY_b0=!volumeup
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Compal
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnCOMPAL:pnHEL80I:*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_84=wlan
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# COMPAQ
###########################################################
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnCompaq*:pn*E500*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnCompaq*:pn*Evo*N*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_a3=www # I key
KEYBOARD_KEY_9a=search
KEYBOARD_KEY_9e=email
KEYBOARD_KEY_9f=homepage
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v049Fp0051*
hwdb: Add mapping for special keys on compaq ku 0133 keyboards The compaq ku 0133 keyboard has 8 special keys at the top: http://lackof.org/taggart/hacking/keyboard/cpqwireless.jpg 3 of these use standard HID usage codes from the consumer page, the 5 others use part of the reserved 0x07 - 0x1f range. This commit adds mapping for this keyboard for these reserved codes, making the other 5 keys work. Cc: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2014-10-22 20:09:21 +08:00
KEYBOARD_KEY_0c0011=presentation
KEYBOARD_KEY_0c0012=addressbook
KEYBOARD_KEY_0c0013=info
KEYBOARD_KEY_0c0014=prog1
KEYBOARD_KEY_0c0015=messenger
hwdb: Cube iwork8 air button keymap fixup The home and power buttons on the Cube iwork8 air tablet are swapped, add a hwdb entry fixing this up. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2017-02-12 19:45:21 +08:00
###########################################################
# Cube
###########################################################
evdev:name:gpio-keys:phys:gpio-keys/input0:ev:3:dmi:bvn*:bvr*:bd*:svncube:pni1-TF:*
hwdb: Fix mapping for home-key on Cube iWork8 air (#5994) The intent of the hwdb entry for the Cube iWork8 air tablet buttons is to fix them being swapped. The kernel is using left-meta for the home key (it is being treated as the windows key on keyboards, as it has a windows logo on most x86 tablets). Fix the hwdb entry to only swap the buttons and not change the keycode emitted by the home key.
2017-05-19 22:05:27 +08:00
KEYBOARD_KEY_0=leftmeta
hwdb: Cube iwork8 air button keymap fixup The home and power buttons on the Cube iwork8 air tablet are swapped, add a hwdb entry fixing this up. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2017-02-12 19:45:21 +08:00
KEYBOARD_KEY_1=power
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# Dell
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pn*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_81=playpause # Play/Pause
KEYBOARD_KEY_82=stopcd # Stop
KEYBOARD_KEY_83=previoussong # Previous song
KEYBOARD_KEY_84=nextsong # Next song
KEYBOARD_KEY_85=brightnessdown # Fn+Down Brightness Down
KEYBOARD_KEY_86=brightnessup # Fn+Up Brightness Up
KEYBOARD_KEY_87=battery # Fn+F3 battery icon
hwdb: revert airplane mode keys handling on Dell That reverts the commits #8762 and #9868, those created double key events issues on some Dell laptops.
2018-11-09 23:54:02 +08:00
KEYBOARD_KEY_88=unknown # Fn+F2 Turn On/Off Wireless - handled in hardware
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_89=ejectclosecd # Fn+F10 Eject CD
KEYBOARD_KEY_8a=suspend # Fn+F1 hibernate
KEYBOARD_KEY_8b=switchvideomode # Fn+F8 CRT/LCD (high keycode: "displaytoggle")
keymap: Fix wrong assignments to F23 These days, F21/F22/F23 mean Touchpad toggle/on/off. Clean up other assignments to that from ancient times which belong to keys like "Auto Brightness" (which doesn't have a keycode and is usually hardwired) or some "launch vendor tool" key. https://bugs.freedesktop.org/show_bug.cgi?id=62953
2013-09-20 05:42:10 +08:00
KEYBOARD_KEY_8c=unknown # Fn+Right Auto Brightness
hwdb: use lowercase hex for key numbers It seems awkward to have both cases mixes. Note that the real parser accepts both cases, and this only standarizes the usage in the systemd database.
2016-08-06 01:31:37 +08:00
KEYBOARD_KEY_8f=switchvideomode # Fn+F7 aspect ratio
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_90=previoussong # Front panel previous song
KEYBOARD_KEY_91=prog1 # Wi-Fi Catcher (Dell-specific)
KEYBOARD_KEY_92=media # MediaDirect button (house icon)
keymap: Fix wrong assignments to F23 These days, F21/F22/F23 mean Touchpad toggle/on/off. Clean up other assignments to that from ancient times which belong to keys like "Auto Brightness" (which doesn't have a keycode and is usually hardwired) or some "launch vendor tool" key. https://bugs.freedesktop.org/show_bug.cgi?id=62953
2013-09-20 05:42:10 +08:00
KEYBOARD_KEY_93=unknown # FIXME Fn+Left Auto Brightness
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_95=camera # Shutter button - Takes a picture if optional camera available
KEYBOARD_KEY_97=email # Tablet email button
KEYBOARD_KEY_98=f21 # FIXME: Tablet screen rotation
KEYBOARD_KEY_99=nextsong # Front panel next song
KEYBOARD_KEY_9a=setup # Tablet tools button
KEYBOARD_KEY_9b=switchvideomode # Display toggle button
KEYBOARD_KEY_9e=f21 # Touchpad toggle
KEYBOARD_KEY_a2=playpause # Front panel play/pause
KEYBOARD_KEY_a4=stopcd # Front panel stop
KEYBOARD_KEY_ed=media # MediaDirect button
KEYBOARD_KEY_d8=screenlock # FIXME: Tablet lock button
KEYBOARD_KEY_d9=f21 # Touchpad toggle
#
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnInspiron*910:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnInspiron*101[012]:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnInspiron*1110:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnInspiron*1210:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_84=wlan
hwdb: Treat Latitude 2110 brightness keys like on Inspiron 1520 (#4355) Like the Inspiron 1520, the Dell Latitude 2110 emits brightness-control key events both through atkbd and acpi-video. This suppresses them on the atkbd side.
2016-10-12 21:41:56 +08:00
# Dell Inspiron 1520 and Latitude 2110
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnInspiron*1520:pvr*
hwdb: Treat Latitude 2110 brightness keys like on Inspiron 1520 (#4355) Like the Inspiron 1520, the Dell Latitude 2110 emits brightness-control key events both through atkbd and acpi-video. This suppresses them on the atkbd side.
2016-10-12 21:41:56 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnLatitude*2110:pvr*
keymap: Ignore brightness keys on Dell Inspiron 1520 to avoid double events On the Dell Inspiron 1520 both the atkbd and acpi-video input devices report an event for pressing the brightness up / down key-combos, resulting in user space seeing double events and increasing / decreasing the brightness 2 steps for each keypress. This hwdb snippet suppresses the atkbd events, making the Inspiron 1520 work like most modern laptops which emit brightness up / down events through acpi-video only. Reported by Pavel Malyshev <p.malishev@gmail.com> https://bugzilla.redhat.com/show_bug.cgi?id=1141525
2014-10-30 17:15:54 +08:00
KEYBOARD_KEY_85=unknown # Brightness Down, also emitted by acpi-video, ignore
KEYBOARD_KEY_86=unknown # Brightness Up, also emitted by acpi-video, ignore
hwdb: revert airplane mode keys handling on Dell That reverts the commits #8762 and #9868, those created double key events issues on some Dell laptops.
2018-11-09 23:54:02 +08:00
# Dell Inspiron 537*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnInspiron537*:pvr*
KEYBOARD_KEY_88=!wlan # Fn-PrtScr rfkill
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Latitude XT2
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnLatitude*XT2:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_9b=up # tablet rocker up
KEYBOARD_KEY_9e=enter # tablet rocker press
KEYBOARD_KEY_9f=back # tablet back
KEYBOARD_KEY_a3=down # tablet rocker down
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnStudio*155[78]:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_a0=! # mute
KEYBOARD_KEY_ae=! # volume down
KEYBOARD_KEY_b0=! # volume up
# Dell Touchpad
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnLatitude*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:pvr*
hwdb: revert airplane mode keys handling on Dell That reverts the commits #8762 and #9868, those created double key events issues on some Dell laptops.
2018-11-09 23:54:02 +08:00
KEYBOARD_KEY_88=! # wireless switch
keymap: Don't erase previous assignments Don't use "KEYBOARD_KEY_xx=!" assignments (i. e. only enabling force-release) if more general matches already explicitly set a key code before, to not override the previously set value. https://launchpad.net/bugs/1218433
2013-08-29 23:48:42 +08:00
KEYBOARD_KEY_9e=!f21
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
hwdb: fix warning "atkbd serio0: Unknown key pressed" (#5772) At each time pressing the WiFi Fn key on Dell Latitude E7270 laptop, the system reports the following error/warning messages: atkbd serio0: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0). atkbd serio0: Use 'setkeycodes e008 ' to make it known. This is due to commit 0e33634 which was added to fix https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1441849. However on Dell Latitude E7* models, we need to restore the old generic behavior which consists in ignoring the key event since it's already done by the HW. Indeed the hardware has a specific driver (dell_wmi) to handle rfkill in the hardware level. So, as long as the hardware handles, the best is to leave as is. This patch was originally written by Takashi Iwai. Fixes #5047
2017-04-21 03:09:13 +08:00
# Dell Latitude E7*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnLatitude*E7*:pvr*
KEYBOARD_KEY_88=unknown # Fn-PrtScr rfkill - handled in HW
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Dell XPS
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnXPS*:pvr*
keymap: Fix wrong assignments to F23 These days, F21/F22/F23 mean Touchpad toggle/on/off. Clean up other assignments to that from ancient times which belong to keys like "Auto Brightness" (which doesn't have a keycode and is usually hardwired) or some "launch vendor tool" key. https://bugs.freedesktop.org/show_bug.cgi?id=62953
2013-09-20 05:42:10 +08:00
KEYBOARD_KEY_8c=!unknown
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
hwdb: add "special" keys on Dell XPS L702x (#8828) Based on information provided by phenest in https://github.com/systemd/systemd/issues/5341. Those keys map to some special functions in windows, so let's map them to prog1/prog2 so the user map them to something. Fixes #5341.
2018-04-27 02:31:11 +08:00
# Dell XPS L702x
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDellInc.:pnDellSystemXPSL702X:pvr*
KEYBOARD_KEY_84=prog1
KEYBOARD_KEY_85=prog2
udev/hwdb: New Entry for Dell XPS12 9Q33 keyboard https://bugs.freedesktop.org/show_bug.cgi?id=84437
2014-09-30 10:32:10 +08:00
# Dell XPS12 9Q33
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnXPS12-9Q33*:pvr*
udev/hwdb: New Entry for Dell XPS12 9Q33 keyboard https://bugs.freedesktop.org/show_bug.cgi?id=84437
2014-09-30 10:32:10 +08:00
KEYBOARD_KEY_88=wlan
hwdb: fix Dell XPS12 9Q33 key name https://bugs.freedesktop.org/show_bug.cgi?id=84437
2015-03-05 09:25:04 +08:00
KEYBOARD_KEY_65=direction # Screen Rotate
udev/hwdb: New Entry for Dell XPS12 9Q33 keyboard https://bugs.freedesktop.org/show_bug.cgi?id=84437
2014-09-30 10:32:10 +08:00
keymap: Add microphone mute keymap for Dell Latitude On the Dell Latitude, the mic mute key event is generated by wmi driver, the keycode assigned to this hotkey from kernel is KEY_MICMUTE (248), this keycode is too big for xorg to handle, in the xorg, the XF86AudioMicMute is assigned to F20. Please refer to 4e648ea0 of xkeyboard-config. BugLink: https://bugs.launchpad.net/bugs/1326684 BugLink: https://bugs.launchpad.net/bugs/1339998 Signed-off-by: Hui Wang <hui.wang@canonical.com> Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
2014-07-30 16:09:08 +08:00
# Dell Latitude microphone mute
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnLatitude*
Add microphone mute keymap for Dell Precision
2015-09-10 11:20:50 +08:00
# Dell Precision microphone mute
evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*
hwdb: update micmute YCODE on device node at DELL LATITUDE laptops for mic mute button. (#5012)
2017-01-11 21:35:20 +08:00
KEYBOARD_KEY_100150=f20 # Mic mute toggle, should be micmute
keymap: Add microphone mute keymap for Dell Latitude On the Dell Latitude, the mic mute key event is generated by wmi driver, the keycode assigned to this hotkey from kernel is KEY_MICMUTE (248), this keycode is too big for xorg to handle, in the xorg, the XF86AudioMicMute is assigned to F20. Please refer to 4e648ea0 of xkeyboard-config. BugLink: https://bugs.launchpad.net/bugs/1326684 BugLink: https://bugs.launchpad.net/bugs/1339998 Signed-off-by: Hui Wang <hui.wang@canonical.com> Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
2014-07-30 16:09:08 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# Everex
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnEverex:pnXT5000*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_5c=media
KEYBOARD_KEY_65=f21 # Fn+F5 Touchpad toggle
KEYBOARD_KEY_67=prog3 # Fan speed control button
KEYBOARD_KEY_6f=brightnessup
KEYBOARD_KEY_7f=brightnessdown
KEYBOARD_KEY_b2=www
KEYBOARD_KEY_ec=mail
##########################################
# Fujitsu
##########################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFUJITSU*:pnAMILO*M*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_97=prog2
KEYBOARD_KEY_9f=prog1
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFUJITSU*:pnAmilo*Li*1718:*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_d6=wlan
# Amilo Li 2732
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFUJITSU*:pnAMILO*Li*2732:*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_d9=brightnessdown # Fn+F8 brightness down
KEYBOARD_KEY_ef=brightnessup # Fn+F9 brightness up
KEYBOARD_KEY_a9=switchvideomode # Fn+F10 Cycle between available video outputs
# Amilo Pa 2548
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFUJITSU*:pn*AMILO*Pa*2548*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_e0=volumedown
KEYBOARD_KEY_e1=volumeup
KEYBOARD_KEY_e5=prog1
# Amilo Pro Edition V3505
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFUJITSU*:pn*AMILO*Pro*Edition*V3505*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_a5=help # Fn+F1
KEYBOARD_KEY_a9=switchvideomode # Fn+F3
KEYBOARD_KEY_d9=brightnessdown # Fn+F8
KEYBOARD_KEY_e0=brightnessup # Fn+F9
# Amilo Pro v3205
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFUJITSU*:pn*AMILO*Pro*V3205*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_f4=f21 # FIXME: silent-mode decrease CPU/GPU clock
KEYBOARD_KEY_f7=switchvideomode # Fn+F3
# Amilo Si 1520
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFUJITSU*:pn*Amilo*Si*1520*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_e1=wlan
KEYBOARD_KEY_f3=wlan
KEYBOARD_KEY_ee=brightnessdown
KEYBOARD_KEY_e0=brightnessup
KEYBOARD_KEY_e2=bluetooth
KEYBOARD_KEY_f7=video
# Esprimo Mobile V5
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFUJITSU*:pn*ESPRIMO*Mobile*V5*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_a9=switchvideomode
KEYBOARD_KEY_d9=brightnessdown
KEYBOARD_KEY_df=sleep
KEYBOARD_KEY_ef=brightnessup
# Esprimo Mobile V6
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFUJITSU*:pn*ESPRIMO*Mobile*V6*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_ce=brightnessup
KEYBOARD_KEY_ef=brightnessdown
hwdb: add GIGABYTE U2442 mute key to the force-release list https://bugs.freedesktop.org/show_bug.cgi?id=67651
2013-08-05 10:46:38 +08:00
###########################################################
# GIGABYTE
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGIGABYTE:pnU2442:*
hwdb: add GIGABYTE U2442 mute key to the force-release list https://bugs.freedesktop.org/show_bug.cgi?id=67651
2013-08-05 10:46:38 +08:00
KEYBOARD_KEY_a0=! # mute
hwdb: Add support for Gemini NC14 keyboard
2019-01-31 21:32:24 +08:00
###########################################################
# Gemini
###########################################################
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGeminiDevices:pnNC14V1006:*
KEYBOARD_KEY_9c=enter
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# Genius
###########################################################
# Slimstar 320
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v0458p0708*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_0900f0=scrollup
KEYBOARD_KEY_0900f1=scrolldown
KEYBOARD_KEY_0900f3=back
KEYBOARD_KEY_0900f2=forward
KEYBOARD_KEY_0900f5=wordprocessor
KEYBOARD_KEY_0900f6=spreadsheet
KEYBOARD_KEY_0900f4=presentation
KEYBOARD_KEY_0c0223=www
KEYBOARD_KEY_0900f7=chat
KEYBOARD_KEY_0900fb=prog1
KEYBOARD_KEY_0900f8=close
KEYBOARD_KEY_0900f9=graphicseditor
KEYBOARD_KEY_0900fd=scale
KEYBOARD_KEY_0900fc=screenlock
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
# Hewlett Packard
###########################################################
hwdb: Mask rfkill event from intel-hid on HP platforms HP spec mandates the hp-wireless driver as canonical source of rfkill event, so mask the rfkill event from intel-hid to avoid double rfkill events fired from a single hotkey press.
2020-06-11 21:32:12 +08:00
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
KEYBOARD_KEY_8=unknown # Use hp-wireless instead
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*:pvr*
keymap: Some HP refactoring, add Probook 440 G3 keys Apparently the vendor string for newer models now uses "svnHP" instead of "svnHewlett-Packard", so add this alternative match to the global HP map. Generalize matches for micmute key on ProBook 4xx. Silence two hardwired keys on the ProBook 440 G3 that should not produce evdev events. Thanks to Hermann Kraus for those! (See PR #2679)
2016-03-01 21:51:29 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_81=fn_esc
KEYBOARD_KEY_89=battery # Fn+F8
KEYBOARD_KEY_8a=screenlock # Fn+F6
KEYBOARD_KEY_8b=camera
KEYBOARD_KEY_8c=media # music
KEYBOARD_KEY_8e=dvd
KEYBOARD_KEY_b1=help
keymap: Fix wrong assignments to F23 These days, F21/F22/F23 mean Touchpad toggle/on/off. Clean up other assignments to that from ancient times which belong to keys like "Auto Brightness" (which doesn't have a keycode and is usually hardwired) or some "launch vendor tool" key. https://bugs.freedesktop.org/show_bug.cgi?id=62953
2013-09-20 05:42:10 +08:00
KEYBOARD_KEY_b3=unknown # FIXME: Auto brightness
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_d7=wlan
KEYBOARD_KEY_92=brightnessdown # Fn+F7 (Fn+F9 on 6730b)
KEYBOARD_KEY_97=brightnessup # Fn+F8 (Fn+F10 on 6730b)
KEYBOARD_KEY_ee=switchvideomode # Fn+F4
# Tablet
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*[tT][aA][bB][lL][eE][tT]*:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_82=prog2 # Funny Key
KEYBOARD_KEY_83=prog1 # Q
KEYBOARD_KEY_84=tab
KEYBOARD_KEY_85=esc
KEYBOARD_KEY_86=pageup
KEYBOARD_KEY_87=pagedown
keymap: add Pavilion dv7 keys
2013-08-16 09:40:56 +08:00
# Pavilion
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*[pP][aA][vV][iI][lL][iI][oO][nN]*:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_88=media # FIXME: quick play
keymap: add Pavilion dv7 keys
2013-08-16 09:40:56 +08:00
KEYBOARD_KEY_b7=print
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_d8=!f23 # touchpad off
KEYBOARD_KEY_d9=!f22 # touchpad on
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHP*Pavilion*dv7*Notebook*PC:pvr*
keymap: add Pavilion dv7 keys
2013-08-16 09:40:56 +08:00
KEYBOARD_KEY_b7=print
KEYBOARD_KEY_c2=media # FIXME: quick play
KEYBOARD_KEY_c6=break
keymap: Fix HP Pavillon DV7 Properly disable scan code 94 instead of producing KEY_0. https://launchpad.net/bugs/1322770
2014-08-05 18:29:27 +08:00
KEYBOARD_KEY_94=reserved
keymap: add Pavilion dv7 keys
2013-08-16 09:40:56 +08:00
hwdb: Pavilion 13 x360: Tablet mode and SYSRQ key
2020-07-04 14:43:34 +08:00
# Pavilion 13 x360 (Tablet mode and SYSRQ key)
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*[pP][aA][vV][iI][lL][iI][oO][nN]*13*x360*:pvr*
KEYBOARD_KEY_d7=!f22 # touchpad off
KEYBOARD_KEY_d9=unknown
KEYBOARD_KEY_d2=sysrq # Fn+Print = SYSRQ
# Spectre x360 13 (Prevents random airplane mode activation)
hwdb: Fix airplane mode triggering when resuming HP Spectre x360 13 On these devices the key randomly fires during/after suspend/resume triggering spurious airplane mode changes. The scancode simply needs to be ignored.
2019-03-09 00:42:23 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*[sS][pP][eE][cC][tT][rR][eE]*x360*13*:pvr*
hwdb: Fix airplane mode spam on HP Spectre x360 Convertible Added additional rule matching my HP Spectre x360 Convertible from 2015 (skylake)
2019-08-13 18:10:56 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*[sS][pP][eE][cC][tT][rR][eE]*x360Convertible*:pvr*
hwdb: fix airplane mode trigger when switching from laptop to desktop on HP Pavilion x360 13 (#4680)
2016-11-17 05:57:20 +08:00
KEYBOARD_KEY_d7=unknown
hwdb: add HP Spectre x360's mic mute switch Tested on HP Spectre x360 Convertible 13-aw0xxx
2020-06-08 18:45:02 +08:00
# Spectre x360 13
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pnHPSpectrex360Convertible13*:pvr*
KEYBOARD_KEY_82=f20 # Fn+F12; Microphone mute button, should be micmute
Prevent triple reporting of rfkill button on HP Elite x2 1013 G3, plus five other hotkeys 1. rfkill hotkey is reported from three source: keyboard, Intel HID and HP Wireless hotkeys. Let's block first two. 2. Correct mapping for calendar, micmute, display and brightness hotkeys.
2020-09-27 09:25:27 +08:00
# HP Elite x2 1013 G3
evdev:atkbd:dmi:bvn*:bvr*:svnHP*:pnHPElitex21013G3:*
KEYBOARD_KEY_f8=unknown # rfkill is also reported by HP Wireless hotkeys
KEYBOARD_KEY_64=calendar
KEYBOARD_KEY_81=f20 # Microphone mute button
KEYBOARD_KEY_ee=switchvideomode # Switch display outputs
KEYBOARD_KEY_92=brightnessdown
KEYBOARD_KEY_97=brightnessup
evdev:name:Intel HID events:dmi:bvn*:bvr*:svnHP*:pnHPElitex21013G3:*
KEYBOARD_KEY_08=unknown # rfkill is also reported by HP Wireless hotkeys
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
# Elitebook
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*Compaq*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*EliteBook*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*2230s*:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_88=presentation
KEYBOARD_KEY_d9=help # I key (high keycode: "info")
# Presario
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*Presario*CQ*:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_d8=f21
KEYBOARD_KEY_d9=f21
# 2510p 2530p
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*2510p*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*2530p*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHP*G60*Notebook*PC:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_d8=!f23 # touchpad off
KEYBOARD_KEY_d9=!f22 # touchpad on
keymap: add HP EliteBook 2570p's wlan switch to hwdb https://bugs.freedesktop.org/show_bug.cgi?id=66178
2013-08-06 09:54:00 +08:00
# 2570p
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*2570p*:pvr*
keymap: add HP EliteBook 2570p's wlan switch to hwdb https://bugs.freedesktop.org/show_bug.cgi?id=66178
2013-08-06 09:54:00 +08:00
KEYBOARD_KEY_f8=wlan # Wireless HW switch button
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
# TX2
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*[tT][xX]2*:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_c2=media
KEYBOARD_KEY_d8=!f23 # Toggle touchpad button on tx2 (OFF)
KEYBOARD_KEY_d9=!f22 # Toggle touchpad button on tx2 (ON)
# Presario 2100
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnPresario*2100*:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_f0=help
KEYBOARD_KEY_f1=screenlock
KEYBOARD_KEY_f3=search
# Elitebook 8440p
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHP*EliteBook*8440p:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_88=www
KEYBOARD_KEY_a0=mute
KEYBOARD_KEY_ae=volumedown
KEYBOARD_KEY_b0=volumeup
KEYBOARD_KEY_ec=mail
# Elitebook 8460p
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHP*EliteBook*8460p:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_f8=wlan # Wireless HW switch button
KEYBOARD_KEY_b3=prog1 # Fn+F11 - Ambient Light Sensor button
KEYBOARD_KEY_b1=prog2 # Fn+ESC - System information button
# HDX9494nr
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHDX9494NR:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_b2=www # Fn+F3
KEYBOARD_KEY_d8=!f23 # touchpad off
KEYBOARD_KEY_d9=!f22 # touchpad on
keymap: Add microphone mute keymap for several HP laptops On these several HP laptops, the microphone mute hotkey is "Fn+F8" and the scancode for this hotkey is 0x81, but this scancode was mapped to fn_esc in the HP generic keymap section. To fix this problem, we add a machine specific keymap section to add the correct keymap rule. BugLink: https://bugs.launchpad.net/bugs/1409721 BugLink: https://bugs.launchpad.net/bugs/1334968 Signed-off-by: Hui Wang <hui.wang@canonical.com>
2015-02-10 16:42:22 +08:00
# HP EliteBook 725 G2
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHPLicrice:pvr*
hwdb: Add EliteBook to use micmute hotkey Like HP ZBooks, all EliteBooks use the same micmute scancode.
2020-06-16 13:24:27 +08:00
# HP EliteBook
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHPEliteBook*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pnHPEliteBook*:pvr*
keymap: Add microphone mute keymap for several HP laptops On these several HP laptops, the microphone mute hotkey is "Fn+F8" and the scancode for this hotkey is 0x81, but this scancode was mapped to fn_esc in the HP generic keymap section. To fix this problem, we add a machine specific keymap section to add the correct keymap rule. BugLink: https://bugs.launchpad.net/bugs/1409721 BugLink: https://bugs.launchpad.net/bugs/1334968 Signed-off-by: Hui Wang <hui.wang@canonical.com>
2015-02-10 16:42:22 +08:00
# HP ProBook 440 G2
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHP440G2:pvr*
keymap: Some HP refactoring, add Probook 440 G3 keys Apparently the vendor string for newer models now uses "svnHP" instead of "svnHewlett-Packard", so add this alternative match to the global HP map. Generalize matches for micmute key on ProBook 4xx. Silence two hardwired keys on the ProBook 440 G3 that should not produce evdev events. Thanks to Hermann Kraus for those! (See PR #2679)
2016-03-01 21:51:29 +08:00
# several HP ProBooks 4xx
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHP*ProBook4*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pnHP*ProBook*4*:pvr*
keymap: Add HP ZBook https://launchpad.net/bugs/1535219
2016-03-01 21:43:43 +08:00
# HP ZBook
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHPZBook*:pvr*
hwdb: HP vendor name for ZBooks in 60-keyboard.hwdb (#7905) Added new HP vendor name to support Zbook's mic mute key mapping
2018-01-17 17:15:00 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBook*:pvr*
keymap: Add microphone mute keymap for several HP laptops On these several HP laptops, the microphone mute hotkey is "Fn+F8" and the scancode for this hotkey is 0x81, but this scancode was mapped to fn_esc in the HP generic keymap section. To fix this problem, we add a machine specific keymap section to add the correct keymap rule. BugLink: https://bugs.launchpad.net/bugs/1409721 BugLink: https://bugs.launchpad.net/bugs/1334968 Signed-off-by: Hui Wang <hui.wang@canonical.com>
2015-02-10 16:42:22 +08:00
KEYBOARD_KEY_81=f20 # Fn+F8; Microphone mute button, should be micmute
hwdb: add missing newline so the hwdb buils correctly again
2016-04-29 16:46:56 +08:00
Add RF kill switch button for Zbook 15 G2 (#11060)
2018-12-10 20:20:46 +08:00
# HP ZBook 15 G2
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHPZBook15G2:pvr*
KEYBOARD_KEY_f8=wlan # Wireless HW switch button
hwdb: Add keymaps for HP ProBook 11 G1 Add microphone-mute and touchpad-toggle keymaps for the HP ProBook 11 G1 notebook. Signed-off-by: Carlo Caione <carlo@endlessm.com> Signed-off-by: João Paulo Rechi Vita <jprvita@endlessm.com>
2016-04-14 23:05:44 +08:00
# HP ProBook 11 G1
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHPProBook11G1:pvr*
KEYBOARD_KEY_81=f20 # Fn+F8; Microphone mute button, should be micmute
KEYBOARD_KEY_d8=f21 # touchpad toggle
KEYBOARD_KEY_d9=f21 # touchpad toggle
hwdb: HP ZBook Studio G4 wireless switch
2018-06-07 17:43:59 +08:00
# HP ZBook Studio G4
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP:pnHPZBookStudioG4:pvr*
KEYBOARD_KEY_f8=wlan # Wireless HW switch button
Calendar and micmute hotkeys on HP EliteBook Folio G1 This commit add calendar and micmute hotkeys for HP EliteBook Folio G1, and also correct name of other laptop from HP EliteBook Folio series - HP EliteBook Folio 1040 G2
2020-09-30 10:07:53 +08:00
# HP EliteBook Folio 1040 G2
Hp Folio 1040g2 micmute and toggle touchpad fn keys fix (#3118) Added HP Folio 1040g2 Fn+F8 MICMUTE FIx
2016-04-26 03:42:35 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHPEliteBookFolio1040G2:pvr*
KEYBOARD_KEY_d8=!f23 # touchpad off
KEYBOARD_KEY_d9=!f22 # touchpad on
hwdb: fix a syntax error in 60-keyboard
2015-10-18 19:09:20 +08:00
Calendar and micmute hotkeys on HP EliteBook Folio G1 This commit add calendar and micmute hotkeys for HP EliteBook Folio G1, and also correct name of other laptop from HP EliteBook Folio series - HP EliteBook Folio 1040 G2
2020-09-30 10:07:53 +08:00
# HP EliteBook Folio G1
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP:pnHPEliteBookFolioG1:pvr*
KEYBOARD_KEY_64=calendar
KEYBOARD_KEY_81=micmute
[hwdb] Add support for HP ProBook 650 wifi switch key (#9260) Add support for HP ProBook 650 wifi switch key
2018-06-25 19:18:13 +08:00
# HP ProBook 650
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHP*ProBook*650*:pvr*
KEYBOARD_KEY_f8=wlan # Wireless HW switch button
keymap: Add HP ProBook 6555b Thanks to Olaf Hering!
2015-10-16 22:30:08 +08:00
# HP ProBook 6555b
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard:pnHPProBook6555b:*
KEYBOARD_KEY_b2=www # Earth
keymap: Add microphone mute keymap for several HP laptops On these several HP laptops, the microphone mute hotkey is "Fn+F8" and the scancode for this hotkey is 0x81, but this scancode was mapped to fn_esc in the HP generic keymap section. To fix this problem, we add a machine specific keymap section to add the correct keymap rule. BugLink: https://bugs.launchpad.net/bugs/1409721 BugLink: https://bugs.launchpad.net/bugs/1334968 Signed-off-by: Hui Wang <hui.wang@canonical.com>
2015-02-10 16:42:22 +08:00
keymap: Add HP ProBook 440 G3 Fixes #2343
2016-01-18 18:01:32 +08:00
# HP ProBook 440 G3
evdev:atkbd:dmi:bvn*:bvr*:svnHP*:pnHP*ProBook*440*G3*
keymap: Add HP ProBook 640 G2 Fixes #2997
2016-04-11 17:17:07 +08:00
# HP ProBook 640 G2
evdev:atkbd:dmi:bvn*:bvr*:svnHP*:pnHP*ProBook*640*G2*
keymap: Some HP refactoring, add Probook 440 G3 keys Apparently the vendor string for newer models now uses "svnHP" instead of "svnHewlett-Packard", so add this alternative match to the global HP map. Generalize matches for micmute key on ProBook 4xx. Silence two hardwired keys on the ProBook 440 G3 that should not produce evdev events. Thanks to Hermann Kraus for those! (See PR #2679)
2016-03-01 21:51:29 +08:00
KEYBOARD_KEY_85=unknown # lid close; also reported via special evdev
KEYBOARD_KEY_f8=unknown # rf kill; also reported via special evdev
keymap: Add HP ProBook 440 G3 Fixes #2343
2016-01-18 18:01:32 +08:00
hwdb: Add support for HP ProBook 645 wifi and slash key (#11207) hwdb: Add support for HP ProBook 645 wifi and slash key
2018-12-20 20:58:02 +08:00
# HP ProBook 645 G4
evdev:atkbd:dmi:bvn*:bvr*:svnHP*:pnHP*ProBook*645*G4*
KEYBOARD_KEY_73=slash # Slash key
KEYBOARD_KEY_f8=wlan # Wireless HW switch button
hwdb: Add key-mapping for GPIO-keys on HP stream 7 tablet (#11631) The HP stream 7 ACPI tables contains a gpio-keys entry for a non connected GPIO causing spurious events, this commit maps this key to unknown to disable it. BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=202279
2019-02-04 06:58:39 +08:00
# HP Stream 7
# The ACPI tables contains a gpio-keys entry for a non connected GPIO
# causing spurious events, map this to unknown to disable it
# older kernels use "ev:23" newer kernels "ev:3"
evdev:name:gpio-keys:phys:gpio-keys/input0:ev:3:dmi:*:svnHewlett-Packard:pnHPStream7Tablet:*
evdev:name:gpio-keys:phys:gpio-keys/input0:ev:23:dmi:*:svnHewlett-Packard:pnHPStream7Tablet:*
KEYBOARD_KEY_0=unknown
hwdb: Add Huawei section and remap keys (#11406) hwdb: Add support for 'Huawei WMI hotkeys' driver Since 'Huawei WMI hotkeys' driver finally got merged into kernel [commit](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86/huawei-wmi.c?id=bf4fb28c6e74495de9e1e4ad359cd2272ac12c53), this remaps 'KEY_MICMUTE' to 'F20' to make the key work and disables brightness keys on (MACH-WX9) since it's already supported by kernel.
2019-01-17 20:47:43 +08:00
##########################################################
# Huawei
##########################################################
# Huawei WMI hotkeys driver
evdev:name:Huawei WMI hotkeys:dmi:bvn*:bvr*:bd*:svnHUAWEI*
KEYBOARD_KEY_287=f20 # Microphone mute button, should be micmute
# Huawei MACH-WX9
evdev:atkbd:dmi:bvn*:bvr*:svnHUAWEI*:pnMACH-WX9:pvr*
KEYBOARD_KEY_f7=unknown
KEYBOARD_KEY_f8=fn
hwdb: fix duplicate events on Huawei MACH-WX9 Signed-off-by: Ayman Bagabas <ayman.bagabas@gmail.com>
2019-01-22 12:50:35 +08:00
evdev:name:Huawei WMI hotkeys:dmi:bvn*:bvr*:bd*:svnHUAWEI*:pnMACH-WX9:pvr*
hwdb: Add Huawei section and remap keys (#11406) hwdb: Add support for 'Huawei WMI hotkeys' driver Since 'Huawei WMI hotkeys' driver finally got merged into kernel [commit](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86/huawei-wmi.c?id=bf4fb28c6e74495de9e1e4ad359cd2272ac12c53), this remaps 'KEY_MICMUTE' to 'F20' to make the key work and disables brightness keys on (MACH-WX9) since it's already supported by kernel.
2019-01-17 20:47:43 +08:00
KEYBOARD_KEY_281=unknown # Brightness Down, also emitted by acpi-video, ignore
KEYBOARD_KEY_282=unknown # Brightness Up, also emitted by acpi-video, ignore
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# IBM
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# thinkpad_acpi driver
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:ThinkPad Extra Buttons:dmi:bvn*:bvr*:bd*:svnIBM*:pn*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_01=battery # Fn+F2
KEYBOARD_KEY_02=screenlock # Fn+F3
KEYBOARD_KEY_03=sleep # Fn+F4
KEYBOARD_KEY_04=wlan # Fn+F5
KEYBOARD_KEY_06=switchvideomode # Fn+F7
KEYBOARD_KEY_07=zoom # Fn+F8 screen expand
KEYBOARD_KEY_08=f24 # Fn+F9 undock
KEYBOARD_KEY_0b=suspend # Fn+F12
KEYBOARD_KEY_0f=brightnessup # Fn+Home
KEYBOARD_KEY_10=brightnessdown # Fn+End
KEYBOARD_KEY_11=kbdillumtoggle # Fn+PgUp - ThinkLight
KEYBOARD_KEY_13=zoom # Fn+Space
KEYBOARD_KEY_14=volumeup
KEYBOARD_KEY_15=volumedown
KEYBOARD_KEY_16=mute
KEYBOARD_KEY_17=prog1 # ThinkPad/ThinkVantage button (high keycode: "vendor")
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# IBM Thinkpad USB Keyboard Trackpoint
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v04B3p301[89]*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_900f0=screenlock
KEYBOARD_KEY_900f1=wlan
KEYBOARD_KEY_900f2=switchvideomode
KEYBOARD_KEY_900f3=suspend
KEYBOARD_KEY_900f4=brightnessup
KEYBOARD_KEY_900f5=brightnessdown
KEYBOARD_KEY_900f8=zoom
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Inventec
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Symphony
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnINVENTEC:pnSYMPHONY*6.0/7.0:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_f3=prog2
KEYBOARD_KEY_f4=prog1
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Lenovo
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# thinkpad_acpi driver
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:ThinkPad Extra Buttons:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_01=screenlock
KEYBOARD_KEY_02=battery
KEYBOARD_KEY_03=sleep
KEYBOARD_KEY_04=wlan
KEYBOARD_KEY_06=switchvideomode
KEYBOARD_KEY_07=f21
KEYBOARD_KEY_08=f24
KEYBOARD_KEY_0b=suspend
KEYBOARD_KEY_0f=brightnessup
KEYBOARD_KEY_10=brightnessdown
KEYBOARD_KEY_11=kbdillumtoggle
KEYBOARD_KEY_13=zoom
KEYBOARD_KEY_14=volumeup
KEYBOARD_KEY_15=volumedown
KEYBOARD_KEY_16=mute
KEYBOARD_KEY_17=prog1
keymap: Annotate all micmute workarounds Add a comment to all assignments to f20 that this actually should be "micmute" in a future when we aren't limited by X.org's key code limiations any more.
2014-07-30 16:54:23 +08:00
KEYBOARD_KEY_1a=f20 # Microphone mute button; should be micmute
hwdb: Map 45 to bookmarks on the ThinkPad L380 The ThinkPad L380 has a F12(Favorate) key. The keycode 0x45 is mapped to KEY_FAVORITES(0x16c) in kernel thinkpad_acpi driver, but this keycode is too big for xorg to handle. xkeyboard-config mapped KEY_BOOKMARKS to XF86Favorites: keycodes/evdev: <I164> = 164; // #define KEY_BOOKMARKS 156 symbols/inet: key <I164> { [ XF86Favorites ] }; So map 45 to bookmarks to correct keycode. Signed-off-by: Zhang Xianwei <zhang.xianwei8@zte.com.cn>
2018-10-09 18:53:25 +08:00
KEYBOARD_KEY_45=bookmarks
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# ThinkPad Keyboard with TrackPoint
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v17EFp6009*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_090012=screenlock # Fn+F2
KEYBOARD_KEY_090013=battery # Fn+F3
KEYBOARD_KEY_090014=wlan # Fn+F5
KEYBOARD_KEY_090016=switchvideomode # Fn+F7
KEYBOARD_KEY_090017=f21 # Fn+F8 touchpad toggle
KEYBOARD_KEY_090019=suspend # Fn+F12
KEYBOARD_KEY_09001a=brightnessup # Fn+Home
KEYBOARD_KEY_09001b=brightnessdown # Fn+End
KEYBOARD_KEY_09001d=zoom # Fn+Space
KEYBOARD_KEY_090011=prog1 # ThinkVantage button
KEYBOARD_KEY_090015=camera # Fn+F6 headset/camera VoIP key ??
KEYBOARD_KEY_090010=f20 # Microphone mute button; should be micmute
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Lenovo 3000
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*3000*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_8b=switchvideomode # Fn+F7 video
KEYBOARD_KEY_96=wlan # Fn+F5 wireless
KEYBOARD_KEY_97=sleep # Fn+F4 suspend
KEYBOARD_KEY_98=suspend # Fn+F12 hibernate
KEYBOARD_KEY_b4=prog1 # Lenovo Care
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: add Lenovo 3000 N200 special key https://bugs.freedesktop.org/show_bug.cgi?id=87377
2014-12-17 11:14:40 +08:00
# "Lenovo Care" Key of the 3000 N200
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO:pn0769AP2:pvr3000N200:*
hwdb: add Lenovo 3000 N200 special key https://bugs.freedesktop.org/show_bug.cgi?id=87377
2014-12-17 11:14:40 +08:00
KEYBOARD_KEY_b4=prog1
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# lenovo-ideapad
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*IdeaPad*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pnS10-*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_81=rfkill # does nothing in BIOS
KEYBOARD_KEY_83=display_off # BIOS toggles screen state
KEYBOARD_KEY_b9=brightnessup # does nothing in BIOS
KEYBOARD_KEY_ba=brightnessdown # does nothing in BIOS
KEYBOARD_KEY_f1=camera # BIOS toggles camera power
KEYBOARD_KEY_f2=f21 # touchpad toggle (key alternately emits F2 and F3)
KEYBOARD_KEY_f3=f21
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Thinkpad X200_Tablet
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrThinkPad*X2*Tablet*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_5d=menu
KEYBOARD_KEY_63=fn
KEYBOARD_KEY_66=screenlock
KEYBOARD_KEY_67=cyclewindows # bezel circular arrow
KEYBOARD_KEY_68=setup # bezel setup / menu
KEYBOARD_KEY_6c=direction # rotate screen
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# ThinkPad X6 Tablet
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrThinkPad*X6*Tablet*
keymap: Fix special keys on ThinkPad X60/X61 Tablet KEY_DIRECTION is mapped to XF86RotateWindows, to rotate the display: http://cgit.freedesktop.org/xkeyboard-config/commit/symbols/inet?id=ec875f6f9b7c4028e11d32b071989c682e6502bd And F13 is mapped to XF86Tools, which is closest to the original toolbox usage: http://cgit.freedesktop.org/xkeyboard-config/tree/symbols/inet?id=7a2c4bed212ebbcc05f3c959aef659ce7dd31fd8#n221
2014-11-13 06:31:08 +08:00
KEYBOARD_KEY_6c=direction # rotate
hwdb: Bind "toolbox" buttons to the Windows key One would expect pressing the button to go to an overview / show applications mode, we thus map it to leftmeta, the Windows key. See https://bugzilla.gnome.org/show_bug.cgi?id=658602#c17
2015-02-05 01:46:10 +08:00
KEYBOARD_KEY_68=leftmeta # toolbox
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_6b=esc # escape
KEYBOARD_KEY_6d=right # right on d-pad
KEYBOARD_KEY_6e=left # left on d-pad
KEYBOARD_KEY_71=up # up on d-pad
KEYBOARD_KEY_6f=down # down on d-pad
KEYBOARD_KEY_69=enter # enter on d-pad
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
keymap: Add support for IBM ThinkPad X41 Tablet Scancode taken from: http://www.thinkwiki.org/wiki/Tablet_Hardware_Buttons#Linux_Support William Jon McCann provided the DMI match. IBM seems to have swapped the version and model of the system: Manufacturer: IBM Product Name: 18666TU Version: ThinkPad X41 Tablet
2014-11-13 06:30:46 +08:00
# ThinkPad X41 Tablet
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnIBM*:pn18666TU:pvr*
keymap: Add support for IBM ThinkPad X41 Tablet Scancode taken from: http://www.thinkwiki.org/wiki/Tablet_Hardware_Buttons#Linux_Support William Jon McCann provided the DMI match. IBM seems to have swapped the version and model of the system: Manufacturer: IBM Product Name: 18666TU Version: ThinkPad X41 Tablet
2014-11-13 06:30:46 +08:00
KEYBOARD_KEY_6c=direction # rotate
hwdb: Bind "toolbox" buttons to the Windows key One would expect pressing the button to go to an overview / show applications mode, we thus map it to leftmeta, the Windows key. See https://bugzilla.gnome.org/show_bug.cgi?id=658602#c17
2015-02-05 01:46:10 +08:00
KEYBOARD_KEY_68=leftmeta # toolbox
keymap: Add support for IBM ThinkPad X41 Tablet Scancode taken from: http://www.thinkwiki.org/wiki/Tablet_Hardware_Buttons#Linux_Support William Jon McCann provided the DMI match. IBM seems to have swapped the version and model of the system: Manufacturer: IBM Product Name: 18666TU Version: ThinkPad X41 Tablet
2014-11-13 06:30:46 +08:00
KEYBOARD_KEY_6b=esc # escape
KEYBOARD_KEY_69=enter # enter on d-pad
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# IdeaPad
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Ideapad extra buttons:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*
hwdb: add two more hotkeys to Lenovo IdeaPad (#6410) Tested on Lenovo IdeaPad E41-15, and both keys work after those two line added.
2017-07-20 20:21:48 +08:00
KEYBOARD_KEY_0d=rfkill # airplane mode switch (toggle all wireless devices)
KEYBOARD_KEY_08=f20 # micmute
keymap: Reorder IdeaPad rules So that they are together in the file.
2013-10-28 19:30:47 +08:00
KEYBOARD_KEY_42=f23
KEYBOARD_KEY_43=f22
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*IdeaPad*Y550*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_95=media
KEYBOARD_KEY_a3=play
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*IdeaPad*U300s*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_f1=f21
keymap: Annotate all micmute workarounds Add a comment to all assignments to f20 that this actually should be "micmute" in a future when we aren't limited by X.org's key code limiations any more.
2014-07-30 16:54:23 +08:00
KEYBOARD_KEY_ce=f20 # micmute
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:svnLENOVO*:pn*IdeaPad*Z370*:pvr*
keymap: Fix stuck keys on Lenovo IdeaPad Z370 https://launchpad.net/bugs/1245189
2013-10-28 19:32:12 +08:00
KEYBOARD_KEY_a0=!mute
KEYBOARD_KEY_ae=!volumedown
KEYBOARD_KEY_b0=!volumeup
Fix volume control keys on Lenovo Yoga S940 With the default config repeated press of fn+VolumeUp or fn+VolumeDown lead to repeated presses even after release, which leads to volume going to 100% or 0%.
2020-03-16 03:24:56 +08:00
# Fix for volume keys on Lenovo Yoga S940
tree-wide: remove spurious whitespace
2020-05-28 15:17:31 +08:00
# For 10th gen it should be pn81Q8 instead of pn81Q7 but
Fix volume control keys on Lenovo Yoga S940 With the default config repeated press of fn+VolumeUp or fn+VolumeDown lead to repeated presses even after release, which leads to volume going to 100% or 0%.
2020-03-16 03:24:56 +08:00
# I don't have a device to test
# perhaps pn81Q* would work for both generations
evdev:atkbd:dmi:bvn*:bvr*:svnLENOVO:pn81Q7*:pvrLenovoYogaS940*
KEYBOARD_KEY_a0=!mute
KEYBOARD_KEY_ae=!volumedown
KEYBOARD_KEY_b0=!volumeup
Added support for touchpad hotkey for Lenovo Y50-70 (#11937)
2019-03-11 17:50:56 +08:00
# Lenovo Y50-70
evdev:atkbd:dmi:bvn*:bvr*:svnLENOVO*:pn*20378*:pvr*
KEYBOARD_KEY_f3=f21 # Fn+F6 (toggle touchpad)
keymap: Reorder IdeaPad rules So that they are together in the file.
2013-10-28 19:30:47 +08:00
# V480
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*Lenovo*V480*:pvr*
keymap: Reorder IdeaPad rules So that they are together in the file.
2013-10-28 19:30:47 +08:00
KEYBOARD_KEY_f1=f21
Micmute Key support of ThinkCentre M820z and M920z (#9619) Micmute Key support of ThinkCentre M820z and M920z There was a ThinkCentre M800z Micmute Key support entry. But on new models M820z and M920z, the lines must change a bit, the keyboard:name... must change to evdev:name. Already tested on the M820z and M920z hardwares. Per Poettering's comment in https://github.com/systemd/systemd/pull/9619, We better combine M800z and M820/M920z entries and use the "evdev" prefix.
2018-07-19 17:30:03 +08:00
# Lenovo ThinkCentre M800z/M820z/M920z AIO machines
keymap: remap microphone mute keycode for Lenovo Thinkcentre M800z This Lenovo machine use codec Line2 to implement a microphone mute button, it depends on the unsolicited interrupt to generate key event, the scan code for this button is assigned to 0x00 in the linux kernel driver, and the keycode is KEY_MICMUTE(248), we need to remap this keycode to KEY_F20 to make this hotkey work in X11. BugLink: https://bugs.launchpad.net/bugs/1531362 Signed-off-by: Hui Wang <hui.wang@canonical.com>
2016-01-06 10:37:53 +08:00
# key_scancode 00 is KEY_MICMUTE
Micmute Key support of ThinkCentre M820z and M920z (#9619) Micmute Key support of ThinkCentre M820z and M920z There was a ThinkCentre M800z Micmute Key support entry. But on new models M820z and M920z, the lines must change a bit, the keyboard:name... must change to evdev:name. Already tested on the M820z and M920z hardwares. Per Poettering's comment in https://github.com/systemd/systemd/pull/9619, We better combine M800z and M820/M920z entries and use the "evdev" prefix.
2018-07-19 17:30:03 +08:00
evdev:name:Microphone Mute Button:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*
keymap: remap microphone mute keycode for Lenovo Thinkcentre M800z This Lenovo machine use codec Line2 to implement a microphone mute button, it depends on the unsolicited interrupt to generate key event, the scan code for this button is assigned to 0x00 in the linux kernel driver, and the keycode is KEY_MICMUTE(248), we need to remap this keycode to KEY_F20 to make this hotkey work in X11. BugLink: https://bugs.launchpad.net/bugs/1531362 Signed-off-by: Hui Wang <hui.wang@canonical.com>
2016-01-06 10:37:53 +08:00
KEYBOARD_KEY_00=f20
keymap: Add Lenovo Enhanced USB Keyboard https://bugs.freedesktop.org/show_bug.cgi?id=77234
2014-05-25 17:57:22 +08:00
# enhanced USB keyboard
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v04B3p301B*
keymap: Add Lenovo Enhanced USB Keyboard https://bugs.freedesktop.org/show_bug.cgi?id=77234
2014-05-25 17:57:22 +08:00
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
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# Logitech
###########################################################
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: Add generic key mapping for Logitech 27 MHz keyboards The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This will allow us to add per model keymappings for the special keys on these keyboards, which may differ per model. This commit adds a default / fallback mapping, assigning the most common meaning of the custom Logitech c10XX keycodes.
2019-04-05 04:39:24 +08:00
# 27MHz wireless keyboards, these all have a PID of 00?? and all send c10xx
# logitech custom consumer usage-page codes. The mappings below are the most
# common, but some mapping may differ, especially the Fn F1-F12 mappings
evdev:input:b0003v046Dp00*
KEYBOARD_KEY_c0183=media # HUT:config, kbd:Media/Music player button
KEYBOARD_KEY_c1001=chat # Messenger button
hwdb: Update generic Logitech 27 MHz keyboard key mappings This commit makes 2 changes to the generic Logitech 27 MHz keyboard keymap: 1. It moves some codes from being keyboard specific to the generic 27MHz mapping table, these codes do not conflict on different models and at least the c1019 - c101b codes are not only used on the MX3000 keyboard, but also on the S510 Remote control 2. Add a bunch of new codes found on the S510 keyboard and S510 remote control
2019-05-12 18:21:33 +08:00
KEYBOARD_KEY_c1002=camera # Webcam button
hwdb: Add generic key mapping for Logitech 27 MHz keyboards The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This will allow us to add per model keymappings for the special keys on these keyboards, which may differ per model. This commit adds a default / fallback mapping, assigning the most common meaning of the custom Logitech c10XX keycodes.
2019-04-05 04:39:24 +08:00
KEYBOARD_KEY_c1003=audio # Music Browser button
KEYBOARD_KEY_c1004=video # Video Browser button
KEYBOARD_KEY_c1005=images # Image Browser button
KEYBOARD_KEY_c100a=documents # Document Browser button
hwdb: Update generic Logitech 27 MHz keyboard key mappings This commit makes 2 changes to the generic Logitech 27 MHz keyboard keymap: 1. It moves some codes from being keyboard specific to the generic 27MHz mapping table, these codes do not conflict on different models and at least the c1019 - c101b codes are not only used on the MX3000 keyboard, but also on the S510 Remote control 2. Add a bunch of new codes found on the S510 keyboard and S510 remote control
2019-05-12 18:21:33 +08:00
KEYBOARD_KEY_c100b=rewind # Rewind button
KEYBOARD_KEY_c100c=fastforward # Fast Forward button
KEYBOARD_KEY_c100f=f14 # Track 1 button → f14 → XF86Launch5
KEYBOARD_KEY_c1010=f15 # Track 2 button → f15 → XF86Launch6
KEYBOARD_KEY_c1011=channeldown # Playlist back button
KEYBOARD_KEY_c1012=channelup # Playlist advance button
hwdb: Add generic key mapping for Logitech 27 MHz keyboards The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This will allow us to add per model keymappings for the special keys on these keyboards, which may differ per model. This commit adds a default / fallback mapping, assigning the most common meaning of the custom Logitech c10XX keycodes.
2019-04-05 04:39:24 +08:00
KEYBOARD_KEY_c1013=camera # Webcam button
KEYBOARD_KEY_c1014=coffee # Status button
KEYBOARD_KEY_c1015=record # Record symbol button
KEYBOARD_KEY_c1016=sound # Flame/CD burning → sound → XF86AudioPreset
KEYBOARD_KEY_c1017=ejectcd # Eject button
KEYBOARD_KEY_c1018=config # Remote-control ico
hwdb: Update generic Logitech 27 MHz keyboard key mappings This commit makes 2 changes to the generic Logitech 27 MHz keyboard keymap: 1. It moves some codes from being keyboard specific to the generic 27MHz mapping table, these codes do not conflict on different models and at least the c1019 - c101b codes are not only used on the MX3000 keyboard, but also on the S510 Remote control 2. Add a bunch of new codes found on the S510 keyboard and S510 remote control
2019-05-12 18:21:33 +08:00
KEYBOARD_KEY_c1019=f14 # Preset 1 → f14 → XF86Launch5
KEYBOARD_KEY_c101a=f15 # Preset 2 → f15 → XF86Launch6
KEYBOARD_KEY_c101b=f16 # Preset 3 → f16 → XF86Launch7
hwdb: Add generic key mapping for Logitech 27 MHz keyboards The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This will allow us to add per model keymappings for the special keys on these keyboards, which may differ per model. This commit adds a default / fallback mapping, assigning the most common meaning of the custom Logitech c10XX keycodes.
2019-04-05 04:39:24 +08:00
KEYBOARD_KEY_c101c=cyclewindows # 2 overlapping windows icon
KEYBOARD_KEY_c101f=zoomout # zoom - button / - side of zoomrocker
KEYBOARD_KEY_c1020=zoomin # zoom + button / + side off zoom rocker
KEYBOARD_KEY_c1021=zoomreset # 100% symbol on kbd left side
KEYBOARD_KEY_c1023=close # [x] symbol on kbd left side
hwdb: Update generic Logitech 27 MHz keyboard key mappings This commit makes 2 changes to the generic Logitech 27 MHz keyboard keymap: 1. It moves some codes from being keyboard specific to the generic 27MHz mapping table, these codes do not conflict on different models and at least the c1019 - c101b codes are not only used on the MX3000 keyboard, but also on the S510 Remote control 2. Add a bunch of new codes found on the S510 keyboard and S510 remote control
2019-05-12 18:21:33 +08:00
KEYBOARD_KEY_c1027=menu # Hamburger menu icon
KEYBOARD_KEY_c1028=angle # Rotate button
hwdb: Add generic key mapping for Logitech 27 MHz keyboards The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This will allow us to add per model keymappings for the special keys on these keyboards, which may differ per model. This commit adds a default / fallback mapping, assigning the most common meaning of the custom Logitech c10XX keycodes.
2019-04-05 04:39:24 +08:00
KEYBOARD_KEY_c1029=shuffle # Shuffle button
hwdb: Update generic Logitech 27 MHz keyboard key mappings This commit makes 2 changes to the generic Logitech 27 MHz keyboard keymap: 1. It moves some codes from being keyboard specific to the generic 27MHz mapping table, these codes do not conflict on different models and at least the c1019 - c101b codes are not only used on the MX3000 keyboard, but also on the S510 Remote control 2. Add a bunch of new codes found on the S510 keyboard and S510 remote control
2019-05-12 18:21:33 +08:00
KEYBOARD_KEY_c102a=back # Back button
KEYBOARD_KEY_c102b=cyclewindows # Empty window icon
hwdb: Add generic key mapping for Logitech 27 MHz keyboards The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This will allow us to add per model keymappings for the special keys on these keyboards, which may differ per model. This commit adds a default / fallback mapping, assigning the most common meaning of the custom Logitech c10XX keycodes.
2019-04-05 04:39:24 +08:00
KEYBOARD_KEY_c102d=www # www text + magnifierglass icon
hwdb: Update generic Logitech 27 MHz keyboard key mappings This commit makes 2 changes to the generic Logitech 27 MHz keyboard keymap: 1. It moves some codes from being keyboard specific to the generic 27MHz mapping table, these codes do not conflict on different models and at least the c1019 - c101b codes are not only used on the MX3000 keyboard, but also on the S510 Remote control 2. Add a bunch of new codes found on the S510 keyboard and S510 remote control
2019-05-12 18:21:33 +08:00
KEYBOARD_KEY_c1031=connect # Pickup phone button → connect → XF86Go
KEYBOARD_KEY_c1032=cancel # Hangup phone button → cancel → Cancel
hwdb: Add generic key mapping for Logitech 27 MHz keyboards The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This will allow us to add per model keymappings for the special keys on these keyboards, which may differ per model. This commit adds a default / fallback mapping, assigning the most common meaning of the custom Logitech c10XX keycodes.
2019-04-05 04:39:24 +08:00
KEYBOARD_KEY_c1041=help # Help text or icon (Fn + F1)
KEYBOARD_KEY_c1042=wordprocessor # Word icon (Fn + F2)
KEYBOARD_KEY_c1043=spreadsheet # Excel icon (Fn + F3)
KEYBOARD_KEY_c1044=presentation # Presentation icon (Fn + F4)
KEYBOARD_KEY_c1045=undo # Undo Icon (Fn + F5)
KEYBOARD_KEY_c1046=redo # Redo Icon (Fn + F6)
KEYBOARD_KEY_c1047=print # Printer Icon (Fn + F7)
KEYBOARD_KEY_c1048=save # Floppy Icon (Fn + F8)
KEYBOARD_KEY_c1049=prog1 # Smartkey A (Fn + F9) → XF86Launch1
KEYBOARD_KEY_c104a=prog2 # Smartkey B (Fn + F10) → XF86Launch2
KEYBOARD_KEY_c104b=prog3 # Smartkey C (Fn + F11) → XF86Launch3
KEYBOARD_KEY_c104c=prog4 # Smartkey D (Fn + F12) → XF86Launch4
hwdb: Add key mappings for Logitech 27 MHz "Cordless Access Keyboard" The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This allows us to add per model keymappings for the special keys on these keyboards. This commit adds such mappings for the "Logitech Cordless Access Keyboard" (modelnumber Y-RH35).
2019-03-23 05:10:32 +08:00
# Cordless Access Keyboard (27 MHz, modelnumber Y-RH35)
evdev:input:b0003v046Dp0042*
KEYBOARD_KEY_c1041=new
KEYBOARD_KEY_c1042=reply
KEYBOARD_KEY_c1043=forward
KEYBOARD_KEY_c1044=send
KEYBOARD_KEY_c1045=previoussong
KEYBOARD_KEY_c1046=nextsong
KEYBOARD_KEY_c1047=playpause
KEYBOARD_KEY_c1048=stopcd
KEYBOARD_KEY_c1049=file
KEYBOARD_KEY_c104a=documents
KEYBOARD_KEY_c104b=images
KEYBOARD_KEY_c104c=audio
hwdb: Add key mappings for Logitech 27 MHz "Cordless Rechargeable Desktop" keyboard The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This allows us to add per model keymappings for the special keys on these keyboards. This commit adds such mappings for the "Logitech Rechargeable Desktop" keyboard (modelnumber Y-RK49).
2019-03-30 06:42:56 +08:00
# "Cordless Rechargeable Desktop" keyboard (27 MHz, modelnumber Y-RK49)
evdev:input:b0003v046Dp0045*
KEYBOARD_KEY_c1041=new
KEYBOARD_KEY_c1042=reply
KEYBOARD_KEY_c1043=forward
KEYBOARD_KEY_c1044=send
KEYBOARD_KEY_c1049=file
KEYBOARD_KEY_c104a=documents
KEYBOARD_KEY_c104b=images
KEYBOARD_KEY_c104c=audio
hwdb: Add key mappings for Logitech S510 keyboard and remote control The S510 keyboard and S510 remote control both have 1 key where the markings on the key dop not match with the generic Logitech 27MHz keymap. This commit adds device specific overrides for this.
2019-05-12 18:25:39 +08:00
# S510 keyboard (27 MHz, modelnumber Y-RAK73)
evdev:input:b0003v046Dp0056*
KEYBOARD_KEY_c1041=battery # Battery icon (Fn + F1)
hwdb: Add key mappings for Logitech 27 MHz MX3000 keyboard The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This allows us to add per model keymappings for the special keys on these keyboards. This commit adds such mappings for the MX3000 keyboard (modelnumber Y-RAM74).
2019-04-04 04:52:06 +08:00
# MX3000 keyboard (27 MHz, modelnumber Y-RAM74)
# We ignore the scroll up / down keypress events since these buttons also
# generate scroll-wheel events and we do not want to generate duplicate events
# Note if the "Special Button Function" in the HID++ features register gets
# cleared then the scroll-wheel events for these buttons go away and then
# tilting the scrollwheel left/right starts sending c1022 / c1024 events
evdev:input:b0003v046Dp0057*
KEYBOARD_KEY_c1041=battery # Battery icon (Fn + F1)
#KEYBOARD_KEY_c101d=scrolldown # Button below scrollwheel (see note above)
#KEYBOARD_KEY_c101e=scrollup # Button above scrollwheel (see note above)
#KEYBOARD_KEY_c1022=scrollleft # Left click on scroll-wheel (see note above)
#KEYBOARD_KEY_c1024=scrollright # Right click on scroll-wheel (see note above)
hwdb: Add key mappings for Logitech 27 MHz MX3200 keyboard The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This allows us to add per model keymappings for the special keys on these keyboards. This commit adds such mappings for the MX3200 keyboard (modelnumber Y-RAV80).
2019-04-05 06:40:40 +08:00
# MX3200 keyboard (27 MHz, modelnumber Y-RAV80)
evdev:input:b0003v046Dp005C*
KEYBOARD_KEY_c1001=phone # VOIP button
KEYBOARD_KEY_c1016=record # Record button
KEYBOARD_KEY_c1041=wordprocessor # Word icon (Fn + F1)
KEYBOARD_KEY_c1042=spreadsheet # Excel icon (Fn + F2)
KEYBOARD_KEY_c1043=calendar # Calendar icon (Fn + F3)
KEYBOARD_KEY_c1044=documents # My Documents icon (Fn + F4)
KEYBOARD_KEY_c1045=prog1 # Smartkey A (Fn + F5) → XF86Launch1
KEYBOARD_KEY_c1046=prog2 # Smartkey B (Fn + F6) → XF86Launch2
KEYBOARD_KEY_c1047=prog3 # Smartkey C (Fn + F7) → XF86Launch3
KEYBOARD_KEY_c1048=prog4 # Smartkey D (Fn + F8) → XF86Launch4
hwdb: Add key mappings for Logitech 27 MHz EX100 keyboard The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This allows us to add per model keymappings for the special keys on these keyboards. This commit adds such mappings for the EX100 keyboard (modelnumber Y-RBH94).
2019-04-05 22:18:03 +08:00
# EX100 keyboard (27 MHz, modelnumber Y-RBH94)
evdev:input:b0003v046Dp0065*
KEYBOARD_KEY_c104b=battery # Battery icon (Fn + F11)
KEYBOARD_KEY_c104c=ejectcd # Eject icon (Fn + F12)
hwdb: Add key mappings for Logitech 27 MHz S520 keyboard The upcoming kernel enumerates Logitech 27 MHz wireless keyboards and mice by there wireless-PID, rather then using the PID of the receiver which is the same for all 27MHz Logitech devices. This allows us to add per model keymappings for the special keys on these keyboards. This commit adds such mappings for the S520 keyboard (modelnumber Y-RBA97).
2019-04-05 20:47:04 +08:00
# S520 keyboard (27 MHz, modelnumber Y-RBA97)
# Note this one uses non-standard codes for FN + F9 - Fn + F12?
evdev:input:b0003v046Dp0066*
KEYBOARD_KEY_c100e=prog4 # Smartkey D (Fn + F12) → XF86Launch4
KEYBOARD_KEY_c1019=prog1 # Smartkey A (Fn + F9) → XF86Launch1
KEYBOARD_KEY_c101a=prog2 # Smartkey B (Fn + F10) → XF86Launch2
KEYBOARD_KEY_c101b=prog3 # Smartkey C (Fn + F11) → XF86Launch3
KEYBOARD_KEY_c1041=wordprocessor # Word icon (Fn + F1)
KEYBOARD_KEY_c1042=spreadsheet # Excel icon (Fn + F2)
KEYBOARD_KEY_c1043=presentation # Presentation icon (Fn + F3)
KEYBOARD_KEY_c1044=calendar # Calendar icon (Fn + F4)
KEYBOARD_KEY_c1045=homepage # Home icon (Fn + F5)
KEYBOARD_KEY_c1046=email # Letter icon (Fn + F6)
KEYBOARD_KEY_c1047=search # Magnifying glass icon (Fn + F7)
KEYBOARD_KEY_c1048=config # Window with gear icon (Fn + F8)
KEYBOARD_KEY_c106f=battery # Battery icon
hwdb: Add key mappings for Logitech S510 keyboard and remote control The S510 keyboard and S510 remote control both have 1 key where the markings on the key dop not match with the generic Logitech 27MHz keymap. This commit adds device specific overrides for this.
2019-05-12 18:25:39 +08:00
# S510 remote control (27 MHz)
evdev:input:b0003v046Dp00FE*
KEYBOARD_KEY_c1018=media # Media button
hwdb: Add key mappings for Logitech MX5000 keyboard Add support for various custom key-codes emitted by the Logitech MX5000 keyboard, both when attached through its Bluetooth-receiver in USB-HID proxy mode; and when connected as a Bluetooth device.
2019-04-02 23:23:12 +08:00
# MX5000 keyboard (HID proxy mode and bluetooth matches)
evdev:input:b0003v046DpB305*
evdev:input:b0005v046DpB305*
KEYBOARD_KEY_c0230=zoomreset # HUT says fullscreen, kbd says 100%
KEYBOARD_KEY_c1004=send # Send and receive / sync button
KEYBOARD_KEY_c1006=coffee # Status (online/away) button
KEYBOARD_KEY_c1007=camera # Webcam button
hwdb: Add LCD menu key mappings for the Logitech MX5000 and MX5500 keyboards The kernel now has proper evdev codes for the menu buttons below the small LCD-s builtin to some keyboards. Add mappings for these buttons on the Logitech MX5000 and MX5500 keyboards.
2019-06-10 01:40:32 +08:00
KEYBOARD_KEY_c100c=kbd_lcd_menu1 # 1st button below the builtin LCD
KEYBOARD_KEY_c100d=kbd_lcd_menu4 # 4th button below the builtin LCD
KEYBOARD_KEY_c100e=kbd_lcd_menu2 # 2nd button below the builtin LCD
KEYBOARD_KEY_c100f=kbd_lcd_menu3 # 3th button below the builtin LCD
hwdb: Add key mappings for Logitech MX5000 keyboard Add support for various custom key-codes emitted by the Logitech MX5000 keyboard, both when attached through its Bluetooth-receiver in USB-HID proxy mode; and when connected as a Bluetooth device.
2019-04-02 23:23:12 +08:00
KEYBOARD_KEY_c1038=prog1 # Smartkey A → XF86Launch1
KEYBOARD_KEY_c1039=prog2 # Smartkey B → XF86Launch2
KEYBOARD_KEY_c103a=prog3 # Smartkey C → XF86Launch3
KEYBOARD_KEY_c103b=prog4 # Smartkey D → XF86Launch4
hwdb: Add key mappings for Logitech MX5500 keyboard Add support for various custom key-codes emitted by the Logitech MX5500 keyboard, both when attached through its Bluetooth-receiver in USB-HID proxy mode; and when connected as a Bluetooth device.
2019-04-29 03:21:00 +08:00
# MX5500 keyboard (HID proxy mode and bluetooth matches)
evdev:input:b0003v046DpB30B*
evdev:input:b0005v046DpB30B*
KEYBOARD_KEY_c0183=media # HUT says consumer control configuration, kbd says Media Center
KEYBOARD_KEY_c100e=images # Camera icon, "Photo Gallery"
KEYBOARD_KEY_c100f=config # Window with gear icon
KEYBOARD_KEY_c1038=prog1 # Smartkey A → XF86Launch1
KEYBOARD_KEY_c1039=prog2 # Smartkey B → XF86Launch2
KEYBOARD_KEY_c103a=prog3 # Smartkey C → XF86Launch3
KEYBOARD_KEY_c103b=prog4 # Smartkey D → XF86Launch4
hwdb: Fix brightness keys for Logitech K811 Closes: #15698
2020-05-05 13:42:21 +08:00
# Logitech K811
evdev:input:b0005v046DpB317*
KEYBOARD_KEY_70047=brightnessdown
KEYBOARD_KEY_70048=brightnessup
keymap: re-add Logitech USB corded/cordless models These add back are the remaining 3 udev keymap rules which used name based instead of ID based matching.
2013-07-16 22:53:35 +08:00
# iTouch
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v046DpC308*
hwdb: data update
2013-07-18 09:05:51 +08:00
KEYBOARD_KEY_90001=shop # Shopping
KEYBOARD_KEY_90002=config # iTouch
KEYBOARD_KEY_90003=finance # Finance
KEYBOARD_KEY_90004=prog1 # My Sites
KEYBOARD_KEY_90005=prog2 # Community
hwdb: use lowercase hex for key numbers It seems awkward to have both cases mixes. Note that the real parser accepts both cases, and this only standarizes the usage in the systemd database.
2016-08-06 01:31:37 +08:00
KEYBOARD_KEY_c0183=media # Media
keymap: re-add Logitech USB corded/cordless models These add back are the remaining 3 udev keymap rules which used name based instead of ID based matching.
2013-07-16 22:53:35 +08:00
# Cordless Desktop S510
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v046DpC50C*
hwdb: map zoomin/out keys to up/down Some keyboards come with a zoom see-saw or rocker which until now got mapped to the Linux "zoomin/out" keys in hwdb. However, these keycodes are not recognized by any major desktop. They now produce Up/Down key events so that they can be used for scrolling. The internet is full of instructions how to "unbreak" these keys, e. g. https://askubuntu.com/questions/471802/make-the-zoom-slider-of-microsoft-natural-ergonomic-keyboard-4000-and-7000-scrol https://unix.stackexchange.com/questions/322075/how-to-get-ms-natural-ergonomic-4000-slider-work-on-linux-mint So let's make it official. But keep their physical meaning in comments in case desktops start to do something useful with them at some point. Thanks to Finn Christiansen for the original patch! Replaces #6953
2018-01-23 04:17:08 +08:00
KEYBOARD_KEY_d4=up # zoomin
KEYBOARD_KEY_cc=down # zoomout
keymap: re-add Logitech USB corded/cordless models These add back are the remaining 3 udev keymap rules which used name based instead of ID based matching.
2013-07-16 22:53:35 +08:00
# Wave cordless
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v046DpC317*
hwdb: data update
2013-07-18 09:05:51 +08:00
KEYBOARD_KEY_9001c=scale # expo
hwdb: map zoomin/out keys to up/down Some keyboards come with a zoom see-saw or rocker which until now got mapped to the Linux "zoomin/out" keys in hwdb. However, these keycodes are not recognized by any major desktop. They now produce Up/Down key events so that they can be used for scrolling. The internet is full of instructions how to "unbreak" these keys, e. g. https://askubuntu.com/questions/471802/make-the-zoom-slider-of-microsoft-natural-ergonomic-keyboard-4000-and-7000-scrol https://unix.stackexchange.com/questions/322075/how-to-get-ms-natural-ergonomic-4000-slider-work-on-linux-mint So let's make it official. But keep their physical meaning in comments in case desktops start to do something useful with them at some point. Thanks to Finn Christiansen for the original patch! Replaces #6953
2018-01-23 04:17:08 +08:00
KEYBOARD_KEY_9001f=down # zoomout
KEYBOARD_KEY_90020=up # zoomin
hwdb: data update
2013-07-18 09:05:51 +08:00
KEYBOARD_KEY_9003d=prog1 # gadget
keymap: re-add Logitech USB corded/cordless models These add back are the remaining 3 udev keymap rules which used name based instead of ID based matching.
2013-07-16 22:53:35 +08:00
KEYBOARD_KEY_90005=camera
KEYBOARD_KEY_90018=media
KEYBOARD_KEY_90041=wordprocessor
KEYBOARD_KEY_90042=spreadsheet
KEYBOARD_KEY_90043=calendar
hwdb: data update
2013-07-18 09:05:51 +08:00
KEYBOARD_KEY_90044=prog2 # fn+f4 (program a)
KEYBOARD_KEY_90045=prog3 # fn+f5 (program b)
KEYBOARD_KEY_90046=prog4 # fn+f6 (program c)
KEYBOARD_KEY_90048=messenger # fn+f8 (msn messenger)
KEYBOARD_KEY_9002d=search # fn+f10 (search www)
KEYBOARD_KEY_9004b=find # fn+f11 (search pc)
keymap: re-add Logitech USB corded/cordless models These add back are the remaining 3 udev keymap rules which used name based instead of ID based matching.
2013-07-16 22:53:35 +08:00
KEYBOARD_KEY_9004c=ejectclosecd
# Wave cordless
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v046DpC517*
hwdb: map zoomin/out keys to up/down Some keyboards come with a zoom see-saw or rocker which until now got mapped to the Linux "zoomin/out" keys in hwdb. However, these keycodes are not recognized by any major desktop. They now produce Up/Down key events so that they can be used for scrolling. The internet is full of instructions how to "unbreak" these keys, e. g. https://askubuntu.com/questions/471802/make-the-zoom-slider-of-microsoft-natural-ergonomic-keyboard-4000-and-7000-scrol https://unix.stackexchange.com/questions/322075/how-to-get-ms-natural-ergonomic-4000-slider-work-on-linux-mint So let's make it official. But keep their physical meaning in comments in case desktops start to do something useful with them at some point. Thanks to Finn Christiansen for the original patch! Replaces #6953
2018-01-23 04:17:08 +08:00
KEYBOARD_KEY_c101f=down # zoomout
KEYBOARD_KEY_c1020=up # zoomin
60-keyboard.hwdb: Fix syntax error Add missing '='.
2013-07-17 00:44:30 +08:00
KEYBOARD_KEY_c1005=camera
KEYBOARD_KEY_c0183=media
KEYBOARD_KEY_c1041=wordprocessor
KEYBOARD_KEY_c1042=spreadsheet
KEYBOARD_KEY_c1043=calendar
hwdb: data update
2013-07-18 09:05:51 +08:00
KEYBOARD_KEY_c1044=prog2 # fn+f4 (program a)
KEYBOARD_KEY_c1045=prog3 # fn+f5 (program b)
KEYBOARD_KEY_c1046=prog4 # fn+f6 (program c)
KEYBOARD_KEY_c1048=messenger # fn+f8 (msn messenger)
KEYBOARD_KEY_c104a=find # fn+f10 (search www)
60-keyboard.hwdb: Fix syntax error Add missing '='.
2013-07-17 00:44:30 +08:00
KEYBOARD_KEY_c104c=ejectclosecd
keymap: re-add Logitech USB corded/cordless models These add back are the remaining 3 udev keymap rules which used name based instead of ID based matching.
2013-07-16 22:53:35 +08:00
# Cordless Wave Pro
hwdb: drop bad definition for Cordless Wave Pro keyboard (#8230) [I'm just submitting the solution originally suggested by @barzog. Nevertheless, this looks pretty straightforward, we don't want to define any keys on a universal receiver. Note that this definition was added back in aedc2eddd16e48d468e6ad0aea2caf00c7d37365, when we didn't yet have support for figuring out what hardware is connected behind a logitech receiver.] In 60-keyboard.hwdb there is a definition of # Cordless Wave Pro evdev:input:b0003v046DpC52[9B]* which in fact not a cordless keyboard but an USB receiver to which different types of keyboard can be connected. The solution is to completely clean definition evdev:input:b0003v046DpC52B* from there. I: Bus=0003 Vendor=046d Product=c52b Version=0111 N: Name="Logitech USB Receiver" P: Phys=usb-0000:00:1d.0-1.8/input1 S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.8/4-1.8:1.1/0003:046D:C52B.0005/input/input20 U: Uniq= H: Handlers=kbd mouse0 event8 B: PROP=0 B: EV=1f B: KEY=3007f 0 0 83ffff17aff32d bf54444600000000 ffff0001 130f978b17c000 6773fad941dfed 9ed68000004400 10000002 B: REL=1c3 B: ABS=100000000 B: MSC=10 Fixed #8095.
2018-02-22 06:21:28 +08:00
evdev:input:b0003v046DpC529*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_0c01b6=camera
KEYBOARD_KEY_0c0183=media
KEYBOARD_KEY_0c0184=wordprocessor
KEYBOARD_KEY_0c0186=spreadsheet
KEYBOARD_KEY_0c018e=calendar
KEYBOARD_KEY_0c0223=homepage
KEYBOARD_KEY_0c01bc=messenger
KEYBOARD_KEY_0c018a=mail
KEYBOARD_KEY_0c0221=search
KEYBOARD_KEY_0c00b8=ejectcd
hwdb: map zoomin/out keys to up/down Some keyboards come with a zoom see-saw or rocker which until now got mapped to the Linux "zoomin/out" keys in hwdb. However, these keycodes are not recognized by any major desktop. They now produce Up/Down key events so that they can be used for scrolling. The internet is full of instructions how to "unbreak" these keys, e. g. https://askubuntu.com/questions/471802/make-the-zoom-slider-of-microsoft-natural-ergonomic-keyboard-4000-and-7000-scrol https://unix.stackexchange.com/questions/322075/how-to-get-ms-natural-ergonomic-4000-slider-work-on-linux-mint So let's make it official. But keep their physical meaning in comments in case desktops start to do something useful with them at some point. Thanks to Finn Christiansen for the original patch! Replaces #6953
2018-01-23 04:17:08 +08:00
KEYBOARD_KEY_0c022d=up # zoomin
KEYBOARD_KEY_0c022e=down # zoomout
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: map logitech R400 presenter keys from powerpoint hotkeys to sensible KEY_ definitions
2013-08-09 03:10:52 +08:00
# Logitech Presenter R400
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v046DpC52D*
hwdb: map logitech R400 presenter keys from powerpoint hotkeys to sensible KEY_ definitions
2013-08-09 03:10:52 +08:00
KEYBOARD_KEY_070029=presentation
KEYBOARD_KEY_07003e=presentation
KEYBOARD_KEY_070037=displaytoggle
keymap: Add Logitech Internet Navigator variant [PID C309] By Albrecht Kolthoff <kolthoff@gmx.net> via linux-hotplug@.
2013-08-27 18:57:01 +08:00
# Internet Navigator
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v046DpC309*
hwdb: normalize spacing in 60-keyboard.hwdb (#3954)
2016-08-13 23:14:58 +08:00
KEYBOARD_KEY_90001=chat # Messenger/SMS
KEYBOARD_KEY_90002=camera # webcam
KEYBOARD_KEY_90003=prog1 # iTouch
KEYBOARD_KEY_90004=shop # Shopping
KEYBOARD_KEY_c0201=new # New (F1)
KEYBOARD_KEY_c0289=reply # Reply mail (F2)
KEYBOARD_KEY_c028b=forwardmail # Forward mail (F3)
KEYBOARD_KEY_c028c=send # Send (F4)
KEYBOARD_KEY_c021a=undo # Undo (F5)
KEYBOARD_KEY_c0279=redo # Redo (F6)
KEYBOARD_KEY_c0208=print # Print (F7)
KEYBOARD_KEY_c0207=save # Save (F8)
KEYBOARD_KEY_c0194=file # My Computer (F9)
KEYBOARD_KEY_c01a7=documents # My Documents (F10)
hwdb: Fix F12 mapping on the Logitech Internet Navigator Many Logitech keyboards have the following special functions on F9-F12: F9: file-browser F10: document-browser F11: image-browser F12: music-browser. These should be bound to: #define KEY_FILE 144 /* AL Local Machine Browser */ #define KEY_DOCUMENTS 235 #define KEY_IMAGES 0x1ba /* AL Image Browser */ #define KEY_AUDIO 0x188 /* AL Audio Browser */ This commit fixes the wrong binding of F12 to KEY_SOUND (which translates to XF86AudioPreset) and removes the ?? comments from both F11 and F12.
2019-04-22 15:15:40 +08:00
KEYBOARD_KEY_c01b6=images # My Pictures (F11)
KEYBOARD_KEY_c01b7=audio # My Music (F12)
keymap: Add Logitech Internet Navigator variant [PID C309] By Albrecht Kolthoff <kolthoff@gmx.net> via linux-hotplug@.
2013-08-27 18:57:01 +08:00
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Maxdata
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Pro 7000
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMAXDATA:pnPro*7000*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_97=prog2
KEYBOARD_KEY_9f=prog1
KEYBOARD_KEY_a0=mute # Fn+F5
KEYBOARD_KEY_82=www
KEYBOARD_KEY_ec=email
KEYBOARD_KEY_ae=volumedown # Fn+Down
KEYBOARD_KEY_b0=volumeup # Fn+Up
KEYBOARD_KEY_df=suspend # Fn+F2
KEYBOARD_KEY_f5=help
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# Medion
###########################################################
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: add multimedia keys for Medion Akoya series (#3918)
2016-08-07 23:45:44 +08:00
# Akoya
hwdb: add multimedia keys for Medion Akoya S3409 (#6062)
2017-06-01 18:16:32 +08:00
evdev:atkbd:dmi:bvn*:bvr*:svnMEDION*:pnS3409*:pvr*
hwdb: add multimedia keys for Medion Akoya series (#3918)
2016-08-07 23:45:44 +08:00
evdev:atkbd:dmi:bvn*:bvr*:svnMedion*:pnAkoya*:pvr*
Fix keys on Medion Akoya P6669
2020-03-12 04:38:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:svnMedion*:pnP6669*:pvr*
hwdb: add multimedia keys for Medion Akoya series (#3918)
2016-08-07 23:45:44 +08:00
KEYBOARD_KEY_a0=!mute
KEYBOARD_KEY_ae=!volumedown
KEYBOARD_KEY_b0=!volumeup
KEYBOARD_KEY_19=!p
KEYBOARD_KEY_df=sleep
hwdb: normalize spacing in 60-keyboard.hwdb (#3954)
2016-08-13 23:14:58 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# FID2060
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMEDION*:pn*FID2060*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_6b=channeldown # Thottle Down
KEYBOARD_KEY_6d=channelup # Thottle Up
# NB-A555
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMEDIONNB:pnA555*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_63=www # N button
KEYBOARD_KEY_66=prog1 # link 1 button
KEYBOARD_KEY_67=email # envelope button
KEYBOARD_KEY_69=prog2 # link 2 button
added working volume buttons for medion erazer...
2019-10-04 05:53:08 +08:00
# Erazer
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMedion*:pnErazer*:pvr*
KEYBOARD_KEY_a0=!mute
KEYBOARD_KEY_ae=!volumedown
KEYBOARD_KEY_b0=!volumeup
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# Microsoft
###########################################################
# Microsoft Natural Ergonomic Keyboard 4000
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v045Ep00DB*
hwdb: map zoomin/out keys to up/down Some keyboards come with a zoom see-saw or rocker which until now got mapped to the Linux "zoomin/out" keys in hwdb. However, these keycodes are not recognized by any major desktop. They now produce Up/Down key events so that they can be used for scrolling. The internet is full of instructions how to "unbreak" these keys, e. g. https://askubuntu.com/questions/471802/make-the-zoom-slider-of-microsoft-natural-ergonomic-keyboard-4000-and-7000-scrol https://unix.stackexchange.com/questions/322075/how-to-get-ms-natural-ergonomic-4000-slider-work-on-linux-mint So let's make it official. But keep their physical meaning in comments in case desktops start to do something useful with them at some point. Thanks to Finn Christiansen for the original patch! Replaces #6953
2018-01-23 04:17:08 +08:00
KEYBOARD_KEY_c022d=up # zoomin
KEYBOARD_KEY_c022e=down # zoomout
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: Add mapping for unknown keycodes on Microsofy Reclusa keyboard Add mapping for unknown keycodes on Microsoft Reclusa keyboard.
2018-10-12 22:52:52 +08:00
# Microsoft (Razer produced) Reclusa keyboard
evdev:input:b0003v1532p0200*
KEYBOARD_KEY_c01c9=shuffle
KEYBOARD_KEY_c01ca=up # zoomin
KEYBOARD_KEY_c01cb=down # zoomout
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
###########################################################
# Micro Star
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMICRO-STAR*:pn*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMicro-Star*:pn*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_a0=mute # Fn+F9
KEYBOARD_KEY_ae=volumedown # Fn+F7
KEYBOARD_KEY_b0=volumeup # Fn+F8
KEYBOARD_KEY_b2=www # e button
KEYBOARD_KEY_df=sleep # Fn+F12
KEYBOARD_KEY_e2=bluetooth # satellite dish2
KEYBOARD_KEY_e4=f21 # Fn+F3 Touchpad disable
KEYBOARD_KEY_ec=email # envelope button
KEYBOARD_KEY_ee=camera # Fn+F6 camera disable
KEYBOARD_KEY_f6=wlan # satellite dish1
KEYBOARD_KEY_f7=brightnessdown # Fn+F4
KEYBOARD_KEY_f8=brightnessup # Fn+F5
KEYBOARD_KEY_f9=search
#
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMICRO-STAR*:pnGE60*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMICRO-STAR*:pnGE70*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMicro-Star*:pn*:pvr*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_c2=ejectcd
hwdb: restore comments about MSI devices Some time ago 95-keymap.rules was replaced by 60-keyboard.hwdb. Original comments for MSI laptops (that were in 95-keymap.rules) were removed, but I think they are important for understanding what's going on. https://bugs.freedesktop.org/show_bug.cgi?id=88412
2015-01-18 00:27:12 +08:00
# some MSI models generate ACPI/input events on the LNXVIDEO input devices,
# plus some extra synthesized ones on atkbd as an echo of actually changing the
# brightness; so ignore those atkbd ones, to avoid loops
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMICRO-STAR*:pn*U-100*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMICRO-STAR*:pn*U100*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMICRO-STAR*:pn*N033:*
hwdb: keyboard: Ignore brightness hotkey presses on MSI VR420 (model MS-1422) (#4696) Add MSI VR420 (model MS-1422) to the list of MSI models which need to ignore brightness hotkey presses, as these are already reported through the acpi-video interface. Bug-link: https://bugzilla.redhat.com/show_bug.cgi?id=1270124 Reported-by: David Dreggors <dadreggors@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2016-11-19 23:07:41 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMicro-Star*:pn*VR420*:pvr*
hwdb: Fix bouncing brightness keys on MSI-PR200 Thanks to djfd for the patch! Fixes #6972
2018-01-27 16:35:19 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMicro-Star*:pn*PR200*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_f7=reserved
KEYBOARD_KEY_f8=reserved
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
hwdb: restore comments about MSI devices Some time ago 95-keymap.rules was replaced by 60-keyboard.hwdb. Original comments for MSI laptops (that were in 95-keymap.rules) were removed, but I think they are important for understanding what's going on. https://bugs.freedesktop.org/show_bug.cgi?id=88412
2015-01-18 00:27:12 +08:00
# MSI Wind U90/U100 generates separate touchpad on/off keycodes so ignore touchpad toggle keycode
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMICRO-STAR*:pnU90/U100:*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_e4=reserved
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
Added MSI Prestige15 A10SC specific keycodes This commit enables the microphone mute button and the screen rotate button, even if the latter is improperly linked. I have documented how to achieve this in https://wiki.archlinux.org/index.php/MSI_P15#Fn_Keys .
2020-07-10 01:12:20 +08:00
# MSI Prestige15 A10SC specific keycodes. Needed for microphone and screen rotation
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMicro-Star*:pn*A10SC*:pvr*
KEYBOARD_KEY_f1=f20
KEYBOARD_KEY_f2=f21
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# MSI
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:MSI Laptop hotkeys:dmi:bvn*:bvr*:bd*:svn*:pnM[iI][cC][rR][oO]-S[tT][aA][rR]*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_0213=f22
KEYBOARD_KEY_0214=f23
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: add corrections for Olimex Teres-I to keyboard hwdb The firmware of the Olimex Teres-I (a DIY laptop kit) seems to have wrong scancodes. Fixes #15003.
2020-03-03 22:59:43 +08:00
###########################################################
# Olimex
###########################################################
# Teres-I
evdev:input:b0003v15BAp003C*
KEYBOARD_KEY_70066=sleep # Fn+F1
KEYBOARD_KEY_700f6=wlan # Fn+F2
KEYBOARD_KEY_700c7=f21 # Fn+F3 touchpad toggle
KEYBOARD_KEY_7006f=brightnessdown # Fn+F7
KEYBOARD_KEY_70070=brightnessup # Fn+F8
KEYBOARD_KEY_7006e=switchvideomode # Fn+F9
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
# OLPC
###########################################################
hwdb: Make the OLPC XO rules also match XO-1.75 Uses the same keyboard, attached to the "Security Processor" P1J core that bit-bangs the PS/2 keyboard protocol.
2019-04-23 21:05:28 +08:00
# XO-1 and XO-1.5
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnOLPC:pnXO:*
hwdb: Make the OLPC XO rules also match XO-1.75 Uses the same keyboard, attached to the "Security Processor" P1J core that bit-bangs the PS/2 keyboard protocol.
2019-04-23 21:05:28 +08:00
# XO-1.75 and XO-1.4 (sp/ is the Security Processor)
evdev:name:AT Translated Set 2 keyboard:phys:sp/serio*/input*:ev:120013:*
hwdb: No LEDs on the OLPC XO keyboard
2019-04-23 21:08:53 +08:00
KEYBOARD_LED_CAPSLOCK=0
KEYBOARD_LED_NUMLOCK=0
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_59=fn
KEYBOARD_KEY_81=fn_esc
KEYBOARD_KEY_f9=camera
KEYBOARD_KEY_f8=sound # Fn+CAMERA = Mic
KEYBOARD_KEY_43=brightnessdown
KEYBOARD_KEY_44=brightnessup
KEYBOARD_KEY_57=volumedown
KEYBOARD_KEY_58=volumeup
KEYBOARD_KEY_bb=f1
KEYBOARD_KEY_bc=f2
KEYBOARD_KEY_bd=f3
KEYBOARD_KEY_be=f4
KEYBOARD_KEY_bf=f5
KEYBOARD_KEY_c0=f6
KEYBOARD_KEY_c1=f7
KEYBOARD_KEY_c2=f8
KEYBOARD_KEY_c3=f9
KEYBOARD_KEY_c4=f10
KEYBOARD_KEY_d8=f12
KEYBOARD_KEY_f7=f13
KEYBOARD_KEY_f6=f14
KEYBOARD_KEY_f5=f15
KEYBOARD_KEY_f4=f16
KEYBOARD_KEY_f3=f17
KEYBOARD_KEY_f2=f18
KEYBOARD_KEY_f1=f19
keymap: Annotate all micmute workarounds Add a comment to all assignments to f20 that this actually should be "micmute" in a future when we aren't limited by X.org's key code limiations any more.
2014-07-30 16:54:23 +08:00
KEYBOARD_KEY_f0=f20 # micmute
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_ef=f21
KEYBOARD_KEY_ee=chat
KEYBOARD_KEY_e4=chat
KEYBOARD_KEY_dd=menu # Frame
KEYBOARD_KEY_da=prog1 # Fn+Frame
KEYBOARD_KEY_d3=delete
KEYBOARD_KEY_d2=insert
KEYBOARD_KEY_c9=pageup
KEYBOARD_KEY_d1=pagedown
KEYBOARD_KEY_c7=home
hwdb: use lowercase hex for key numbers It seems awkward to have both cases mixes. Note that the real parser accepts both cases, and this only standarizes the usage in the systemd database.
2016-08-06 01:31:37 +08:00
KEYBOARD_KEY_cf=end
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_73=hp
KEYBOARD_KEY_7e=hp
KEYBOARD_KEY_db=leftmeta # left grab
KEYBOARD_KEY_dc=rightmeta # right grab
KEYBOARD_KEY_85=rightmeta # Right grab releases on a different scancode
KEYBOARD_KEY_d6=kbdillumtoggle # Fn+Space
hwdb: Fix the OLPC XO rotate key The comment is incorrect -- this key code is sent by the rotate button, the brightness keys are separate.
2019-04-23 21:09:04 +08:00
KEYBOARD_KEY_69=rotate_display
hwdb: Fix the key codes of the OLPC XO button pad These are not on a key pad. These codes are sent by the "rocker" buttons that resemble a game pad.
2019-04-23 21:09:17 +08:00
KEYBOARD_KEY_65=btn_dpad_up
KEYBOARD_KEY_66=btn_dpad_down
KEYBOARD_KEY_67=btn_dpad_left
KEYBOARD_KEY_68=btn_dpad_right
KEYBOARD_KEY_e5=btn_north
KEYBOARD_KEY_e6=btn_south
KEYBOARD_KEY_e7=btn_west
KEYBOARD_KEY_e8=btn_east
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
# Onkyo
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnONKYO*CORPORATION:pnONKYOPC:*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_a0=mute # Fn+D
KEYBOARD_KEY_ae=volumedown # Fn+F
KEYBOARD_KEY_b0=volumeup # Fn+G
KEYBOARD_KEY_df=sleep # Fn+W
KEYBOARD_KEY_e0=bluetooth # Fn+H
KEYBOARD_KEY_e2=cyclewindows # Fn+Esc
KEYBOARD_KEY_ee=battery # Fn+Q
KEYBOARD_KEY_f0=media # Fn+R
KEYBOARD_KEY_f5=switchvideomode # Fn+E
KEYBOARD_KEY_f6=camera # Fn+T
KEYBOARD_KEY_f7=f21 # Fn+Y (touchpad toggle)
KEYBOARD_KEY_f8=brightnessup # Fn+S
KEYBOARD_KEY_f9=brightnessdown # Fn+A
KEYBOARD_KEY_fb=wlan # Fn+J
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# OQO
###########################################################
# Model 2
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnOQO*Inc.*:pnOQO*Model*2*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_8e=wlan
KEYBOARD_KEY_f0=switchvideomode
KEYBOARD_KEY_f1=mute
KEYBOARD_KEY_f2=volumedown
KEYBOARD_KEY_f3=volumeup
hwdb: Add Adesso AKB-805MAC keyboard, mfd by Ortek
2020-09-03 08:38:38 +08:00
###########################################################
# Ortek
###########################################################
# Adesso AKB-805MAC
# The key code identifiers used below exactly match the text
# labels on the keys/buttons (or standard icons on the buttons
# that have no text labels), except as noted.
evdev:input:b0003v05A4p9735*
KEYBOARD_KEY_c0015=back
KEYBOARD_KEY_c0012=forward
KEYBOARD_KEY_c000c=stop
KEYBOARD_KEY_c0018=refresh
KEYBOARD_KEY_c00b9=search
KEYBOARD_KEY_c0006=bookmarks # Button labeled "Favorites"
KEYBOARD_KEY_c00a8=homepage # Button labeled "Web/Home"
KEYBOARD_KEY_c0010=mute
KEYBOARD_KEY_c0011=volumedown
KEYBOARD_KEY_c0014=volumeup
KEYBOARD_KEY_c000e=close
KEYBOARD_KEY_c00a7=print
KEYBOARD_KEY_c0013=documents # Button labeled "Stickies"
KEYBOARD_KEY_c000d=find # Button labeled "Sherlock2"
KEYBOARD_KEY_c000f=mail
KEYBOARD_KEY_c000a=calc
KEYBOARD_KEY_c000b=sleep
KEYBOARD_KEY_c0007=previoussong # Button with standard |<< icon
KEYBOARD_KEY_c0008=playpause # Button with standad >/|| icon
KEYBOARD_KEY_c0009=nextsong # Button with standard >>| icon
KEYBOARD_KEY_c00b2=stopcd # Button with standard square box icon
KEYBOARD_KEY_c0016=prog1 # Key labeled "pf1"
KEYBOARD_KEY_c00bb=prog2 # Key labeled "pf2"
KEYBOARD_KEY_c00b8=prog3 # Key labeled "pf3"
keyboard: add Plantronics .Audio mute button https://bugs.freedesktop.org/show_bug.cgi?id=79495
2014-06-02 02:01:23 +08:00
###########################################################
# Plantronics
###########################################################
# Plantronics .Audio 626 DSP
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:input:b0003v047FpC006*
keyboard: add Plantronics .Audio mute button https://bugs.freedesktop.org/show_bug.cgi?id=79495
2014-06-02 02:01:23 +08:00
KEYBOARD_KEY_b002f=f20 # Microphone mute button; should be micmute
Fix for alphabetical ordering (#8581) I read the addition of the purism laptop keyboard and noticed that the 60-keyboard.hwdb file could/should have an alphabetical ordering. I scratched that itch with this commit.
2018-03-26 23:50:35 +08:00
###########################################################
# Purism
###########################################################
# Purism Librem 13 V2
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnPurism*:pn*Librem13v2*:pvr*
KEYBOARD_KEY_56=backslash
hwdb: fix backlash/pipe on Librem 13v3
2018-06-18 04:03:19 +08:00
# Purism Librem 13 V3
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnPurism*:pn*Librem13v3*:pvr*
hwdb: Add support for Purism Librem 13 V4 keyboards
2019-01-22 07:43:22 +08:00
KEYBOARD_KEY_56=backslash
# Purism Librem 13 V4
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnPurism*:pn*Librem13v4*:pvr*
hwdb: fix backlash/pipe on Librem 13v3
2018-06-18 04:03:19 +08:00
KEYBOARD_KEY_56=backslash
Fix for alphabetical ordering (#8581) I read the addition of the purism laptop keyboard and noticed that the 60-keyboard.hwdb file could/should have an alphabetical ordering. I scratched that itch with this commit.
2018-03-26 23:50:35 +08:00
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
# Quanta
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn*:pn*:pvr*:rvnQuanta:rn30B7:rvr65.2B:*
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
KEYBOARD_KEY_88=media # "quick play
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Samsung
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_74=prog1 # User key
KEYBOARD_KEY_75=www
KEYBOARD_KEY_78=mail
KEYBOARD_KEY_82=!switchvideomode # Fn+F4 CRT/LCD (high keycode: "displaytoggle")
KEYBOARD_KEY_83=!battery # Fn+F2
KEYBOARD_KEY_84=!prog1 # Fn+F5 backlight on/off
KEYBOARD_KEY_86=!wlan # Fn+F9
KEYBOARD_KEY_88=!brightnessup # Fn+Up
KEYBOARD_KEY_89=!brightnessdown # Fn+Down
KEYBOARD_KEY_b1=!prog2 # Fn+F7 run Samsung Magic Doctor (keypressed event is generated twice)
KEYBOARD_KEY_b3=!prog3 # Fn+F8 switch power mode (battery/dynamic/performance)
KEYBOARD_KEY_b4=!wlan # Fn+F9 (X60P)
keymap: Add Samsung Series 5 [Ultra] Also consolidate the wlan key into the "all Samsung" rule to avoid repetition. Thanks to Mauro Carvalho Chehab! https://bugzilla.redhat.com/show_bug.cgi?id=989103
2013-09-17 03:25:44 +08:00
KEYBOARD_KEY_c5=!prog3 # Fn+F8 switch power mode (battery/dynamic/performance)
KEYBOARD_KEY_d5=!wlan # Fn+F12 wlan/airplane switch
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_f7=!f22 # Fn+F10 Touchpad on
KEYBOARD_KEY_f9=!f23 # Fn+F10 Touchpad off
# Series 3
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*300E[457]*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*200E[45]*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_ce=! # Fn+F1 launch control setting
Keyboard map for Samsung NP700Z3C I'm using Ubuntu 13.04 on a Samsung Series 5 computer and found that that Fn hotkeys does not work.
2013-08-23 22:18:36 +08:00
# Series 5
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*530U*:pvr*
keymap: Add Samsung Series 5 [Ultra] Also consolidate the wlan key into the "all Samsung" rule to avoid repetition. Thanks to Mauro Carvalho Chehab! https://bugzilla.redhat.com/show_bug.cgi?id=989103
2013-09-17 03:25:44 +08:00
KEYBOARD_KEY_ce=!prog1 # Fn+F1 launch settings
KEYBOARD_KEY_a8=! # Fn Lock - Function lock on
KEYBOARD_KEY_a9=! # Fn Lock - Function lock off
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*550P*:pvr*
keymap: Add Samsung Series 5 [Ultra] Also consolidate the wlan key into the "all Samsung" rule to avoid repetition. Thanks to Mauro Carvalho Chehab! https://bugzilla.redhat.com/show_bug.cgi?id=989103
2013-09-17 03:25:44 +08:00
KEYBOARD_KEY_ce=!prog1 # Fn+F1 launch settings
KEYBOARD_KEY_a8=! # Fn Lock - Function lock on
KEYBOARD_KEY_a9=! # Fn Lock - Function lock off
hwdb: keymaps for Samsung 900X3E/900X3F Keymaps for Samsung 900X3E and 900X3F should be the same as for other models in the series. I have also moved the comment for '# Series 9' to the right place
2014-02-27 13:32:57 +08:00
# Series 7 / 9
keymap: Add Samsung NP350V and NP670Z typo keymap: Add Samsung NP350V and NP670Z
2015-06-10 18:18:22 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*350V*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*670Z*:pvr*
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*700Z*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*700G*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*900X[34]*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*940X3G*:pvr*
Keyboard map for Samsung NP700Z3C I'm using Ubuntu 13.04 on a Samsung Series 5 computer and found that that Fn hotkeys does not work.
2013-08-23 22:18:36 +08:00
KEYBOARD_KEY_ce=!prog1 # Fn+F1 launch settings
KEYBOARD_KEY_a0=!mute # Fn+F6 mute
KEYBOARD_KEY_ae=!volumedown # Fn+F7
KEYBOARD_KEY_b0=!volumeup # Fn+F8
KEYBOARD_KEY_97=!kbdillumdown # Fn+F9 keyboard backlight down
KEYBOARD_KEY_96=!kbdillumup # Fn+F10 keyboard backlight up
KEYBOARD_KEY_b3=!prog3 # Fn+F11 fan/cooling mode changer
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*900X[34][AB]*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_ce=! # Fn+F8 keyboard backlight up
KEYBOARD_KEY_8d=! # Fn+F7 keyboard backlight down
KEYBOARD_KEY_96=! # Fn+F1 performance mode (?)
KEYBOARD_KEY_97=! # Fn+F12 Wi-Fi toggle
KEYBOARD_KEY_d5=! # Fn+F6 battery life extender
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*90X3A*:pvr*
hwdb: change key mappings for Samsung 90X3A The Key codes didn't match with the described key. Also the key identifier strings were missing. I hope I chose appropriate ones. https://bugs.freedesktop.org/show_bug.cgi?id=70296
2014-01-07 08:44:08 +08:00
KEYBOARD_KEY_ce=!prog1 # Fn+F1 launch settings
KEYBOARD_KEY_8d=!prog3 # Fn+F6 performance mode
KEYBOARD_KEY_97=!kbdillumdown # Fn+F7 keyboard backlight down
KEYBOARD_KEY_96=!kbdillumup # Fn+F8 keyboard backlight up
KEYBOARD_KEY_d5=!wlan # Fn+F12 Wi-Fi toggle
Add hwdb entry for Samsung Series 7 Ultra
2014-03-27 09:48:13 +08:00
# Series 7 Ultra
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*7[34]0U3E*:pvr*
Add hwdb entry for Samsung Series 7 Ultra
2014-03-27 09:48:13 +08:00
KEYBOARD_KEY_ce=!prog1 # Fn+F1 launch settings
KEYBOARD_KEY_97=!kbdillumdown # Fn+F9 keyboard backlight down
KEYBOARD_KEY_96=!kbdillumup # Fn+F10 keyboard backlight up
KEYBOARD_KEY_b3=!prog3 # Fn+F11 fan/cooling mode changer
KEYBOARD_KEY_d5=!wlan # Fn+F12 wlan/airplane switch
hwdb: add Samsung ATIV Book 6 / 8 This adds support for the keyboard illumination keys and fixes Fn+F1.
2015-04-07 18:30:10 +08:00
# ATIV Book 6 / 8
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*[68][78]0Z*:pvr*
KEYBOARD_KEY_ce=!prog1 # Fn+F1 launch settings
KEYBOARD_KEY_96=!kbdillumup # Fn+F10 keyboard backlight up
KEYBOARD_KEY_97=!kbdillumdown # Fn+F9 keyboard backlight down
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# SQ1US
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pnSQ1US:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_d4=menu
KEYBOARD_KEY_d8=f1
KEYBOARD_KEY_d9=f10
KEYBOARD_KEY_d6=f3
KEYBOARD_KEY_d7=f9
KEYBOARD_KEY_e4=f5
KEYBOARD_KEY_ee=f11
# SX20S
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*SX20S*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_74=mute
KEYBOARD_KEY_75=mute
KEYBOARD_KEY_77=f22 # Touchpad on
KEYBOARD_KEY_79=f23 # Touchpad off
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn[sS][aA][mM][sS][uU][nN][gG]*:pn*700T*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_ad=leftmeta
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# SONY
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# sony-laptop driver
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_06=mute # Fn+F2
KEYBOARD_KEY_07=volumedown # Fn+F3
KEYBOARD_KEY_08=volumeup # Fn+F4
KEYBOARD_KEY_09=brightnessdown # Fn+F5
KEYBOARD_KEY_0a=brightnessup # Fn+F6
KEYBOARD_KEY_0b=switchvideomode # Fn+F7
KEYBOARD_KEY_0e=zoom # Fn+F10
KEYBOARD_KEY_10=suspend # Fn+F12
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*PCG-C1*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*PCG-K25*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*PCG-F[1-6]*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*PCG-FX*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*PCG-FRV*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*PCG-GR*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*PCG-TR*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*PCG-NV*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*PCG-Z*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pn*VGN-S360*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_06=battery
KEYBOARD_KEY_07=mute
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pnVGN-AR71*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pnVGN-FW*:pvr*
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pnVGN-Z21*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_00=brightnessdown # Fn+F5
KEYBOARD_KEY_10=brightnessup # Fn+F6
KEYBOARD_KEY_11=switchvideomode # Fn+F7
hwdb: map zoomin/out keys to up/down Some keyboards come with a zoom see-saw or rocker which until now got mapped to the Linux "zoomin/out" keys in hwdb. However, these keycodes are not recognized by any major desktop. They now produce Up/Down key events so that they can be used for scrolling. The internet is full of instructions how to "unbreak" these keys, e. g. https://askubuntu.com/questions/471802/make-the-zoom-slider-of-microsoft-natural-ergonomic-keyboard-4000-and-7000-scrol https://unix.stackexchange.com/questions/322075/how-to-get-ms-natural-ergonomic-4000-slider-work-on-linux-mint So let's make it official. But keep their physical meaning in comments in case desktops start to do something useful with them at some point. Thanks to Finn Christiansen for the original patch! Replaces #6953
2018-01-23 04:17:08 +08:00
KEYBOARD_KEY_12=down # zoomout
KEYBOARD_KEY_14=up # zoomin
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_15=suspend # Fn+F12
KEYBOARD_KEY_17=prog1
KEYBOARD_KEY_20=media
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pnVGN-FW250*:pvr*
keymap: Add Sony Vaio VGN-FW250 https://launchpad.net/bugs/1271163
2014-01-29 01:14:18 +08:00
KEYBOARD_KEY_10=suspend # Fn+F12
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Sony Vaio Keys:dmi:bvn*:bvr*:bd*:svnSony*:pnVPC*:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_05=f21 # Fn+F1 -> KEY_F21 (The actual touchpad toggle)
hwdb: map zoomin/out keys to up/down Some keyboards come with a zoom see-saw or rocker which until now got mapped to the Linux "zoomin/out" keys in hwdb. However, these keycodes are not recognized by any major desktop. They now produce Up/Down key events so that they can be used for scrolling. The internet is full of instructions how to "unbreak" these keys, e. g. https://askubuntu.com/questions/471802/make-the-zoom-slider-of-microsoft-natural-ergonomic-keyboard-4000-and-7000-scrol https://unix.stackexchange.com/questions/322075/how-to-get-ms-natural-ergonomic-4000-slider-work-on-linux-mint So let's make it official. But keep their physical meaning in comments in case desktops start to do something useful with them at some point. Thanks to Finn Christiansen for the original patch! Replaces #6953
2018-01-23 04:17:08 +08:00
KEYBOARD_KEY_0d=down # Fn+F9 zoomout
KEYBOARD_KEY_0e=up # Fn+F10 zoomin
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
Add System76 touchpad toggle support
2019-08-21 23:31:35 +08:00
###########################################################
# System76
###########################################################
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnSystem76*:pn*
KEYBOARD_KEY_f7=f21 # Touchpad toggle
KEYBOARD_KEY_f8=f21 # Touchpad toggle
hwdb: Add quirk to fix mapping of T-bao Tbook air touchpad toggle key The touchpad toggle key (Fn + Esc) on the T-bao Tbook air sends CTRL + META + scancode 0x76 without this quirk. With this quirk it sends CTRL + META + F21, with F21 mapping to XF86TouchpadToggle, which is what we want. Note that the CTRL + META modifiers being send together with the F21 are still somewhat unusual, userspace will need to be thought to deal with this as there is nothing we can do about this at the hwdb level. Note at least one other laptop also sends CTRL + META + F21 instead of just F21. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2018-02-20 01:24:09 +08:00
###########################################################
# T-bao
###########################################################
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnT-bao:pnTbookair:pvr*
KEYBOARD_KEY_76=f21 # Touchpad toggle
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Toshiba
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# Satellite A100
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnTOSHIBA*:pnSATELLITE*A100:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_a4=stopcd
KEYBOARD_KEY_b2=www
# Satellite A110
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnTOSHIBA*:pnSatellite*A110:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_92=stop
KEYBOARD_KEY_93=www
KEYBOARD_KEY_94=media
KEYBOARD_KEY_9e=f22 # Touchpad on
KEYBOARD_KEY_9f=f23 # Touchpad off
KEYBOARD_KEY_b9=nextsong
KEYBOARD_KEY_d9=brightnessup
KEYBOARD_KEY_ee=screenlock
KEYBOARD_KEY_f4=previoussong
KEYBOARD_KEY_f7=playpause
# Satellite M30X
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnTOSHIBA*:pnSatellite*M30X:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_ef=brightnessdown
KEYBOARD_KEY_d9=brightnessup
KEYBOARD_KEY_ee=screenlock
KEYBOARD_KEY_93=media
KEYBOARD_KEY_9e=f22 # touchpad enable
KEYBOARD_KEY_9f=f23 # touchpad disable
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: add Toshiba Satellite P75-A Contributed by Guillermo Dominguez Duarte <guillermod84@gmail.com>.
2013-09-12 19:59:34 +08:00
# Satellite P75-A
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnTOSHIBA*:pnSatellite*P75-A:pvr*
hwdb: add Toshiba Satellite P75-A Contributed by Guillermo Dominguez Duarte <guillermod84@gmail.com>.
2013-09-12 19:59:34 +08:00
KEYBOARD_KEY_ef=brightnessdown
KEYBOARD_KEY_ee=brightnessup
KEYBOARD_KEY_a9=switchvideomode # switch display outputs
KEYBOARD_KEY_d4=wlan # RF Switch Off
keymap: Add Toshiba Satellite U940 Signed-off-by: Martin Pitt <martinpitt@gnome.org>
2013-11-18 04:11:34 +08:00
# Satellite U940
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Toshiba*input*device:dmi:bvn*:bvr*:bd*:svnTOSHIBA*:pnSATELLITEU940:pvr*
keymap: Add Toshiba Satellite U940 Signed-off-by: Martin Pitt <martinpitt@gnome.org>
2013-11-18 04:11:34 +08:00
KEYBOARD_KEY_13c=brightnessdown
KEYBOARD_KEY_13d=brightnessup
KEYBOARD_KEY_13e=switchvideomode
KEYBOARD_KEY_13f=f21 # Touchpad toggle
hwdb: Add support for Toshiba Satellite P75-A7200 keyboard
2014-01-11 22:19:41 +08:00
# Satellite P75-A7200
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:name:Toshiba*input*device:dmi:bvn*:bvr*:bd*:svnTOSHIBA*:pnSatellite*P75-A:pvr*
hwdb: Add support for Toshiba Satellite P75-A7200 keyboard
2014-01-11 22:19:41 +08:00
KEYBOARD_KEY_13c=brightnessdown
KEYBOARD_KEY_13d=brightnessup
KEYBOARD_KEY_13e=switchvideomode
keymap: Fix touchpad toggle on Toshiba Satellite P75-A7200 Just like everywhere else we use KEY_F21 instead of KEY_TOUCHPAD_TOGGLE for X friendliness.
2014-10-07 17:20:04 +08:00
KEYBOARD_KEY_13f=f21 # Touchpad toggle
hwdb: Add support for Toshiba Satellite P75-A7200 keyboard
2014-01-11 22:19:41 +08:00
KEYBOARD_KEY_9e=wlan
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
# VIA
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnVIA:pnK8N800:pvr*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_81=prog1
hwdb: Add quirk to fix mapping of VIOS LTH17 touchpad toggle key The touchpad toggle key (Fn + F6) on the VIOS LTH17 sends CTRL + META + F24 without this quirk. With this quirk it sends CTRL + META + F21, with F21 mapping to XF86TouchpadToggle, which is what we want. Note that the CTRL + META modifiers being send together with the F21 are still somewhat unusual, userspace will need to be thought to deal with this as there is nothing we can do about this at the hwdb level. Note at least one other laptop also sends CTRL + META + F21 instead of just F21.
2018-02-20 01:11:30 +08:00
###########################################################
# VIOS
###########################################################
evdev:name:SIPODEV USB Composite Device:dmi:bvn*:bvr*:bd*:svnVIOS:pnLTH17:pvr*
KEYBOARD_KEY_70073=f21 # Touchpad toggle
hwdb: Fix touchpad toggle on WeiHeng P325J On the WeiHeng P325J laptop, Fn+F2 sends LeftWindow (0xe0 0x5b) + LeftCtrl (0x1d) + F24 (0x76). Add a quirk to remap the 0x76 to F21 which toggles the touchpad. The Ctrl + Win part is handled in userspace, e.g by gnome-settings-daemon here: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/f545950fe This is analogous to what was done for the T-bao hardware here: https://github.com/systemd/systemd/commit/d4a5df521d
2020-02-07 08:30:25 +08:00
###########################################################
# WeiHeng
###########################################################
# P325J
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnINET:pnP325J:pvr*
KEYBOARD_KEY_76=f21 # Touchpad toggle
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
###########################################################
# Zepto
###########################################################
# Znote
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnZepto:pnZnote:*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_93=switchvideomode # Fn+F3 Toggle Video Output
KEYBOARD_KEY_95=brightnessdown # Fn+F4 Brightness Down
KEYBOARD_KEY_91=brightnessup # Fn+F5 Brightness Up
KEYBOARD_KEY_a5=f23 # Fn+F6 Disable Touchpad
KEYBOARD_KEY_a6=f22 # Fn+F6 Enable Touchpad
KEYBOARD_KEY_a7=bluetooth # Fn+F10 Enable Bluetooth
KEYBOARD_KEY_a9=bluetooth # Fn+F10 Disable Bluetooth
KEYBOARD_KEY_f1=wlan # RF Switch Off
KEYBOARD_KEY_f2=wlan # RF Switch On
KEYBOARD_KEY_f4=prog1 # P1 Button
KEYBOARD_KEY_f3=prog2 # P2 Button
KEYBOARD_KEY_a0=! # mute
KEYBOARD_KEY_ae=! # volume down
KEYBOARD_KEY_b0=! # volume up
# Znote 6615WD
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnZepto:pnZnote*6615WD:*
hwdb: keyboard update
2013-07-15 06:56:18 +08:00
KEYBOARD_KEY_a0=! # mute
KEYBOARD_KEY_ae=! # volume down
KEYBOARD_KEY_b0=! # volume up
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: add Ideazon Zboard Merc and Ideazon Zboard Fang (#6954)
2018-01-23 04:41:11 +08:00
##########################################
# Ideazon
##########################################
# Ideazon Zboard Merc
evdev:input:b0003v1038p0210*
KEYBOARD_KEY_c0227=q
KEYBOARD_KEY_c0223=w
KEYBOARD_KEY_c0221=e
KEYBOARD_KEY_c0224=a
KEYBOARD_KEY_c0226=s
KEYBOARD_KEY_c0225=d
KEYBOARD_KEY_c0192=tab
KEYBOARD_KEY_c018a=leftalt
KEYBOARD_KEY_c022a=r
KEYBOARD_KEY_c0183=f10
KEYBOARD_KEY_70059=1
KEYBOARD_KEY_7005a=2
KEYBOARD_KEY_7005b=3
KEYBOARD_KEY_7005c=4
KEYBOARD_KEY_7005d=5
KEYBOARD_KEY_7005e=6
KEYBOARD_KEY_7005f=7
KEYBOARD_KEY_70060=8
KEYBOARD_KEY_70061=9
KEYBOARD_KEY_70062=0
KEYBOARD_KEY_70057=equal
KEYBOARD_KEY_70077=capslock
KEYBOARD_KEY_70054=leftshift
KEYBOARD_KEY_70063=leftctrl
KEYBOARD_KEY_7006b=t
KEYBOARD_KEY_70067=f
KEYBOARD_KEY_7006c=g
KEYBOARD_KEY_7006d=v
KEYBOARD_KEY_7006e=b
KEYBOARD_KEY_70074=p
KEYBOARD_KEY_7006f=c
KEYBOARD_KEY_70055=space
KEYBOARD_KEY_70076=f9
KEYBOARD_KEY_70046=f11
KEYBOARD_KEY_70079=f6
# Ideazon Zboard Fang
evdev:input:b0003v1038p0310*
KEYBOARD_KEY_70059=1
KEYBOARD_KEY_7005b=3
KEYBOARD_KEY_70040=equal
KEYBOARD_KEY_70042=l
KEYBOARD_KEY_7002b=tab
KEYBOARD_KEY_7005e=capslock
KEYBOARD_KEY_700e2=leftalt
KEYBOARD_KEY_700e1=leftshift
KEYBOARD_KEY_700e0=leftctrl
KEYBOARD_KEY_70038=z
KEYBOARD_KEY_7003e=t
KEYBOARD_KEY_70015=r
KEYBOARD_KEY_70010=g
KEYBOARD_KEY_70050=n
KEYBOARD_KEY_70030=f9
KEYBOARD_KEY_7002f=f11
KEYBOARD_KEY_70046=f6
hwdb: whitespace fix to make "ninja test" work again Fixes: #7975
2018-01-23 21:32:50 +08:00
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
###########################################################
# Other
###########################################################
hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.
2013-07-12 18:20:18 +08:00
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
# Common Volume Keys
udev: builtin-keyboard: add support for EVDEV_ABS_* Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19 12:19:58 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFUJITSU*SIEMENS:pnAMILO*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnFOXCONN:pnQBOOK:*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMTC:pn*:pvrA0:*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnMio*Technology:pnN890:*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnPEGATRON*CORP.:pnSpring*Peak:*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnTOSHIBA:pnSatellite*[uU][35]0[05]*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnTOSHIBA:pnSATELLITE*[uU][35]0[05]*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnTOSHIBA:pnSatellite*Pro*[uU]300*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnTOSHIBA:pnEQUIUM [uU][35]0[05]*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnViooo*Corporation:pnPT17:*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHANNspree:pnSN10E100:*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGIGABYTE:pni1520M:*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnBenQ:pn*nScreen*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnBenQ:pnJoybook*Lite*:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDIXONSP:pnDIXON*:pvr*
hwdb: keyboard -- update comments
2013-07-12 19:44:08 +08:00
KEYBOARD_KEY_a0=! # mute
KEYBOARD_KEY_ae=! # volume down
KEYBOARD_KEY_b0=! # volume up
hwdb: add XKB_FIXED_LAYOUT/VARIANT to the keyboard hwdb Yubikeys and other pseudo keyboards require that they are in the US layout, otherwise the data they send is invalid. Add two new keys to signal this to processes that handles (XKB) layouts.
2016-11-22 13:21:24 +08:00
hwdb: Better documentation for keyboard quirks Split up the device matching explanation, and add documentation for the fixed layout quirk.
2017-03-09 21:47:53 +08:00
######################### FIXED LAYOUT DEVICES #############################
# This section lists devices for which only one keyboard layout is possible
# or useful such as devices which "type" expecting the user's keymap to match
# a particular one. For example, barcode readers and OTP keys.
#
# The layout must be an xkb compatible layout (defined with XKB_FIXED_LAYOUT),
# with an accompanying variant (defined with XKB_FIXED_VARIANT) if necessary.
hwdb: add XKB_FIXED_LAYOUT/VARIANT to the keyboard hwdb Yubikeys and other pseudo keyboards require that they are in the US layout, otherwise the data they send is invalid. Add two new keys to signal this to processes that handles (XKB) layouts.
2016-11-22 13:21:24 +08:00
# Yubico Yubico Yubikey II"
evdev:input:b0003v1050p0010*
# Yubico Yubikey NEO OTP+CCID
evdev:input:b0003v1050p0111*
hwdb: Add fixed layout for another Yubikey
2016-12-06 19:14:40 +08:00
# Yubico Yubikey NEO OTP+U2F+CCID
evdev:input:b0003v1050p0116*
hwdb: Add fixed layout for OKE barcode reader
2016-12-06 18:42:23 +08:00
# OKE Electron Company USB barcode reader
evdev:input:b0003v05FEp1010*
hwdb: add XKB_FIXED_LAYOUT/VARIANT to the keyboard hwdb Yubikeys and other pseudo keyboards require that they are in the US layout, otherwise the data they send is invalid. Add two new keys to signal this to processes that handles (XKB) layouts.
2016-11-22 13:21:24 +08:00
XKB_FIXED_LAYOUT="us"
XKB_FIXED_VARIANT=""
hwdb: Add property for keyboards without LEDs It is useful for desktop environments to be able to show Caps-Lock or Num-Lock status changes as an on-screen display when using a keyboard that doesn't have LEDs for this. Closes: #5559
2017-03-09 21:53:52 +08:00
######################### LACK OF MODIFIER LEDS ############################
# This section lists keyboard which do not have their own LEDs for some
# modifiers. Only Caps-Lock (KEYBOARD_LED_CAPSLOCK) and Num-Lock
# (KEYBOARD_LED_CAPSLOCK) are currently handled and need their values set
# to "0" to indicate the absence of LED.
#
# Presence of a LED is implicit when the property is absent.
# Logitech K750
evdev:input:b0003v046Dp4002*
KEYBOARD_LED_NUMLOCK=0
KEYBOARD_LED_CAPSLOCK=0
hwdb: ThinkPad T450s doesn't have a caps lock led (#8433)
2018-03-19 22:56:11 +08:00
hwdb: add HHKB Pro JP keyboard lack of LEDs The HHKB Pro JP has no leds whatsoever, record that. The sysfs file "capabilities/led" says "1f".
2019-07-23 21:41:20 +08:00
# PFU Limited HHKB Professional JP
evdev:input:b0003v04FEp000D*
KEYBOARD_LED_NUMLOCK=0
KEYBOARD_LED_CAPSLOCK=0
hwdb: ThinkPad 4x0s and X1 Carbon 3rd gen LEDs (#8492)
2018-03-20 14:41:19 +08:00
# Lenovo ThinkPad T430s
hwdb: add missinging ":*" suffix I'm keeping this part separate because a function change is intended here. Those patterns didn't match: $ systemd-hwdb query 'evdev:atkbd:dmi:bvn_:bvr_:bd_:svnLENOVO:pn_:pvrThinkPadT430s' KEYBOARD_LED_CAPSLOCK=0 $ systemd-hwdb query 'evdev:atkbd:dmi:bvn_:bvr_:bd_:svnLENOVO:pn_:pvrThinkPadT430s:' (nil)
2020-10-15 19:35:36 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO:pn*:pvrThinkPadT430s:*
hwdb: ThinkPad 4x0s and X1 Carbon 3rd gen LEDs (#8492)
2018-03-20 14:41:19 +08:00
KEYBOARD_LED_CAPSLOCK=0
# Lenovo ThinkPad T440s
hwdb: add missinging ":*" suffix I'm keeping this part separate because a function change is intended here. Those patterns didn't match: $ systemd-hwdb query 'evdev:atkbd:dmi:bvn_:bvr_:bd_:svnLENOVO:pn_:pvrThinkPadT430s' KEYBOARD_LED_CAPSLOCK=0 $ systemd-hwdb query 'evdev:atkbd:dmi:bvn_:bvr_:bd_:svnLENOVO:pn_:pvrThinkPadT430s:' (nil)
2020-10-15 19:35:36 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO:pn*:pvrThinkPadT440s:*
hwdb: ThinkPad 4x0s and X1 Carbon 3rd gen LEDs (#8492)
2018-03-20 14:41:19 +08:00
KEYBOARD_LED_CAPSLOCK=0
hwdb: ThinkPad T450s doesn't have a caps lock led (#8433)
2018-03-19 22:56:11 +08:00
# Lenovo ThinkPad T450s
hwdb: add missinging ":*" suffix I'm keeping this part separate because a function change is intended here. Those patterns didn't match: $ systemd-hwdb query 'evdev:atkbd:dmi:bvn_:bvr_:bd_:svnLENOVO:pn_:pvrThinkPadT430s' KEYBOARD_LED_CAPSLOCK=0 $ systemd-hwdb query 'evdev:atkbd:dmi:bvn_:bvr_:bd_:svnLENOVO:pn_:pvrThinkPadT430s:' (nil)
2020-10-15 19:35:36 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO:pn*:pvrThinkPadT450s:*
hwdb: ThinkPad T450s doesn't have a caps lock led (#8433)
2018-03-19 22:56:11 +08:00
KEYBOARD_LED_CAPSLOCK=0
hwdb: ThinkPad T560 doesn't have a caps lock led (#8490) Similar to 16bed3afa1b916ace5e927392a1baab9dd9ff963, this model also doesn't have the LED. ``` cat /sys/class/dmi/id/modalias dmi:bvnLENOVO:bvrN1KET16W(1.03):bd01/20/2016:svnLENOVO:pn20FH001AMX:pvrThinkPadT560:rvnLENOVO:rn20FH001AMX:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: ```
2018-03-20 02:19:53 +08:00
# Lenovo ThinkPad T560s
hwdb: add missinging ":*" suffix I'm keeping this part separate because a function change is intended here. Those patterns didn't match: $ systemd-hwdb query 'evdev:atkbd:dmi:bvn_:bvr_:bd_:svnLENOVO:pn_:pvrThinkPadT430s' KEYBOARD_LED_CAPSLOCK=0 $ systemd-hwdb query 'evdev:atkbd:dmi:bvn_:bvr_:bd_:svnLENOVO:pn_:pvrThinkPadT430s:' (nil)
2020-10-15 19:35:36 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO:pn*:pvrThinkPadT560s:*
hwdb: ThinkPad T560 doesn't have a caps lock led (#8490) Similar to 16bed3afa1b916ace5e927392a1baab9dd9ff963, this model also doesn't have the LED. ``` cat /sys/class/dmi/id/modalias dmi:bvnLENOVO:bvrN1KET16W(1.03):bd01/20/2016:svnLENOVO:pn20FH001AMX:pvrThinkPadT560:rvnLENOVO:rn20FH001AMX:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: ```
2018-03-20 02:19:53 +08:00
KEYBOARD_LED_CAPSLOCK=0
KEYBOARD_LED_NUMLOCK=0
hwdb: ThinkPad 4x0s and X1 Carbon 3rd gen LEDs (#8492)
2018-03-20 14:41:19 +08:00
# Lenovo ThinkPad X1 Carbon 3rd Gen
hwdb: add missinging ":*" suffix I'm keeping this part separate because a function change is intended here. Those patterns didn't match: $ systemd-hwdb query 'evdev:atkbd:dmi:bvn_:bvr_:bd_:svnLENOVO:pn_:pvrThinkPadT430s' KEYBOARD_LED_CAPSLOCK=0 $ systemd-hwdb query 'evdev:atkbd:dmi:bvn_:bvr_:bd_:svnLENOVO:pn_:pvrThinkPadT430s:' (nil)
2020-10-15 19:35:36 +08:00
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO:pn*:pvrThinkPadX1Carbon3rd:*
hwdb: ThinkPad 4x0s and X1 Carbon 3rd gen LEDs (#8492)
2018-03-20 14:41:19 +08:00
KEYBOARD_LED_CAPSLOCK=0
hwdb: add XKB_FIXED_MODEL to the keyboard hwdb Chromebook keyboards have a top row which generates f1-f10 key codes but the keys have media symbols printed on them. A simple scan code to key code mapping to the correct media keys makes the f1-f10 inaccessible. To properly use the keyboard a custom key code to symbol mapping in xbk is required (a variant of the chromebook xkb model is already upstream). Other devices have similar problems. This commit makes it possible to specify which xkb model should be used for a specific device by setting XKB_FIXED_MODEL.
2019-10-31 21:27:24 +08:00
######################### FIXED MODEL DEVICES #############################
# This section lists devices which require special handling in their key
# code to keysym mapping by setting the xkb model.
# The model must be an xkb compatible model (defined with XKB_FIXED_MODEL).
# Chromebooks
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnFalco:pvr*
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:pvr*
XKB_FIXED_MODEL="chromebook"
Reference in New Issue Copy Permalink