mirrors/systemd
0
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-23 10:13:34 +08:00
Code Issues Packages Projects Releases Wiki Activity
main
systemd/hwdb.d/60-input-id.hwdb

92 lines
2.7 KiB
Plaintext
Raw Permalink Normal View History

hwdb: add a hwdb file to override ID_INPUT assignments The input_id builtin assigns the various ID_INPUT based on the exported evdev bits. In some cases, the device may not have the properties required to label a device as one specific type but the physical form factor is clear. e.g. in the case of #7197 it's a tablet pad that does not have x/y axes which the kernel exports for pads for historical reasons. A custom override is needed, best to be solved with a hwdb entry. Related #7197
2017-10-30 08:42:29 +08:00
# This file is part of systemd.
#
# The lookup keys are composed in:
# 60-input-id.rules
#
# Match string formats:
Partially revert "hwdb: reindent commments and say that "*" should always be trailing" This partially reverts commit 62ad1c6495c098a09b36bb20bb37a9b8a11df76f. I kept the reindents and other cosmetic changes, but removed the statements about trailing ":*".
2020-11-03 21:28:14 +08:00
# id-input:modalias:<modalias>
hwdb: add a hwdb file to override ID_INPUT assignments The input_id builtin assigns the various ID_INPUT based on the exported evdev bits. In some cases, the device may not have the properties required to label a device as one specific type but the physical form factor is clear. e.g. in the case of #7197 it's a tablet pad that does not have x/y axes which the kernel exports for pads for historical reasons. A custom override is needed, best to be solved with a hwdb entry. Related #7197
2017-10-30 08:42:29 +08:00
#
# To add local entries, create a new file
# /etc/udev/hwdb.d/61-input-id-local.hwdb
# and add your rules there. To load the new rules execute (as root):
# systemd-hwdb update
# udevadm trigger /dev/input/eventXX
# where /dev/input/eventXX is the device in question. If in
# doubt, simply use /dev/input/event* to reload all input rules.
#
# 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
# udevadm info /dev/input/eventXX.
#
# This file must only be used where the input_id builtin assigns the wrong
hwdb: reindent commments and say that "*" should always be trailing
2020-10-15 15:22:35 +08:00
# properties or lacks the assignment of some properties. This is almost always
# caused by a device not adhering to the standard of the device's type.
hwdb: add a hwdb file to override ID_INPUT assignments The input_id builtin assigns the various ID_INPUT based on the exported evdev bits. In some cases, the device may not have the properties required to label a device as one specific type but the physical form factor is clear. e.g. in the case of #7197 it's a tablet pad that does not have x/y axes which the kernel exports for pads for historical reasons. A custom override is needed, best to be solved with a hwdb entry. Related #7197
2017-10-30 08:42:29 +08:00
#
# Allowed properties are:
hwdb: reindent commments and say that "*" should always be trailing
2020-10-15 15:22:35 +08:00
# ID_INPUT, ID_INPUT_ACCELEROMETER, ID_INPUT_MOUSE, ID_INPUT_POINTINGSTICK,
# ID_INPUT_TOUCHSCREEN, ID_INPUT_TOUCHPAD, ID_INPUT_TABLET,
# ID_INPUT_TABLET_PAD, ID_INPUT_JOYSTICK, ID_INPUT_KEY, ID_INPUT_KEYBOARD,
# ID_INPUT_SWITCH, ID_INPUT_TRACKBALL
hwdb: add a hwdb file to override ID_INPUT assignments The input_id builtin assigns the various ID_INPUT based on the exported evdev bits. In some cases, the device may not have the properties required to label a device as one specific type but the physical form factor is clear. e.g. in the case of #7197 it's a tablet pad that does not have x/y axes which the kernel exports for pads for historical reasons. A custom override is needed, best to be solved with a hwdb entry. Related #7197
2017-10-30 08:42:29 +08:00
#
# ID_INPUT
# * MUST be set when ANY of ID_INPUT_* is set
# * MUST be unset when ALL of ID_INPUT_* are unset
#
# ID_INPUT_TABLET
# * MUST be set when setting ID_INPUT_TABLET_PAD
#
hwdb: reindent commments and say that "*" should always be trailing
2020-10-15 15:22:35 +08:00
# Allowed values are 1 and 0 to set or unset, respectively.
hwdb: add a hwdb file to override ID_INPUT assignments The input_id builtin assigns the various ID_INPUT based on the exported evdev bits. In some cases, the device may not have the properties required to label a device as one specific type but the physical form factor is clear. e.g. in the case of #7197 it's a tablet pad that does not have x/y axes which the kernel exports for pads for historical reasons. A custom override is needed, best to be solved with a hwdb entry. Related #7197
2017-10-30 08:42:29 +08:00
#
# NOT allowed in this file are:
# ID_INPUT_WIDTH_MM, ID_INPUT_HEIGHT_MM, ID_INPUT_TOUCHPAD_INTEGRATION
#
# Example:
Partially revert "hwdb: add trailing ":*" everywhere" This reverts commit c0443b97b71d5f70a0622061f589307bec5502c6. I got various cases wrong: "usb:v04F3p2B7Cd5912dc00dsc00dp00ic03isc00ip00in00" "usb:v0627p0001:QEMU USB Tablet" "input:b0003v0627p0001e0001-e0,1,2,4,k110,111,112,r0,1,8,B,am4,lsfw" OTOH: -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* is OK. Other parts follow after 'pn'. -mouse:*:name:*Trackball*:* -mouse:*:name:*trackball*:* -mouse:*:name:*TrackBall*:* +mouse:*:name:*Trackball*: +mouse:*:name:*trackball*: +mouse:*:name:*TrackBall*: ... and anything else with :name should be OK too, because our imports always include ":" at the end: IMPORT{builtin}="hwdb 'joystick:$env{ID_BUS}:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'" Including '*' at the end makes the pattern work even if we decide to add something to the match string later. Fixes #17499.
2020-11-03 21:17:53 +08:00
# id-input:modalias:input:b0003v1234pABCD*
hwdb: add a hwdb file to override ID_INPUT assignments The input_id builtin assigns the various ID_INPUT based on the exported evdev bits. In some cases, the device may not have the properties required to label a device as one specific type but the physical form factor is clear. e.g. in the case of #7197 it's a tablet pad that does not have x/y axes which the kernel exports for pads for historical reasons. A custom override is needed, best to be solved with a hwdb entry. Related #7197
2017-10-30 08:42:29 +08:00
# ID_INPUT_TOUCHPAD=1
# ID_INPUT=1
# Sort by brand, model
hwdb: add UC-Logic 20160N pad to the ID_INPUT hwdb Missing the x/y axes usually exported for pad devices (for historical reaons) and thus not recognised as tablet (pad). Fixes #7197 See also https://bugs.freedesktop.org/show_bug.cgi?id=103395
2017-10-30 08:58:00 +08:00
hwdb: explicitly label the XP-PEN STAR 06 as tablet Exports BTN_LEFT...BTN_FORWARD, BTN_TOUCH, REL_X/Y/WHEEL/MISC and ABS_X/Y/PRESSURE. Rather than figure out what builtin-input_id tweak we need for this device, just add the tablet bit. https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/issues/8
2018-08-14 10:59:06 +08:00
# XP-PEN STAR 06
Partially revert "hwdb: add trailing ":*" everywhere" This reverts commit c0443b97b71d5f70a0622061f589307bec5502c6. I got various cases wrong: "usb:v04F3p2B7Cd5912dc00dsc00dp00ic03isc00ip00in00" "usb:v0627p0001:QEMU USB Tablet" "input:b0003v0627p0001e0001-e0,1,2,4,k110,111,112,r0,1,8,B,am4,lsfw" OTOH: -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* is OK. Other parts follow after 'pn'. -mouse:*:name:*Trackball*:* -mouse:*:name:*trackball*:* -mouse:*:name:*TrackBall*:* +mouse:*:name:*Trackball*: +mouse:*:name:*trackball*: +mouse:*:name:*TrackBall*: ... and anything else with :name should be OK too, because our imports always include ":" at the end: IMPORT{builtin}="hwdb 'joystick:$env{ID_BUS}:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'" Including '*' at the end makes the pattern work even if we decide to add something to the match string later. Fixes #17499.
2020-11-03 21:17:53 +08:00
id-input:modalias:input:b0003v28bdp0078*
hwdb: explicitly label the XP-PEN STAR 06 as tablet Exports BTN_LEFT...BTN_FORWARD, BTN_TOUCH, REL_X/Y/WHEEL/MISC and ABS_X/Y/PRESSURE. Rather than figure out what builtin-input_id tweak we need for this device, just add the tablet bit. https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/issues/8
2018-08-14 10:59:06 +08:00
ID_INPUT_TABLET=1
hwdb: label the trackpoint on IBM UltraNav keyboard as a pointing stick (#11934) This is the TrackPoint on an older IBM-branded ThinkPad-y USB keyboard. It needs ID_INPUT_POINTINGSTICK=1 for TrackPoint scrolling to work, and also for the AttrTrackpointMultiplier quirk to apply in libinput (otherwise the TrackPoint is too slooooow).
2019-03-11 07:00:03 +08:00
# Lite-On Tech IBM USB Travel Keyboard with Ultra Nav Mouse
Partially revert "hwdb: add trailing ":*" everywhere" This reverts commit c0443b97b71d5f70a0622061f589307bec5502c6. I got various cases wrong: "usb:v04F3p2B7Cd5912dc00dsc00dp00ic03isc00ip00in00" "usb:v0627p0001:QEMU USB Tablet" "input:b0003v0627p0001e0001-e0,1,2,4,k110,111,112,r0,1,8,B,am4,lsfw" OTOH: -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* is OK. Other parts follow after 'pn'. -mouse:*:name:*Trackball*:* -mouse:*:name:*trackball*:* -mouse:*:name:*TrackBall*:* +mouse:*:name:*Trackball*: +mouse:*:name:*trackball*: +mouse:*:name:*TrackBall*: ... and anything else with :name should be OK too, because our imports always include ":" at the end: IMPORT{builtin}="hwdb 'joystick:$env{ID_BUS}:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'" Including '*' at the end makes the pattern work even if we decide to add something to the match string later. Fixes #17499.
2020-11-03 21:17:53 +08:00
id-input:modalias:input:b0003v04B3p301Ee0100-e0,1,2,4*
hwdb: label the trackpoint on IBM UltraNav keyboard as a pointing stick (#11934) This is the TrackPoint on an older IBM-branded ThinkPad-y USB keyboard. It needs ID_INPUT_POINTINGSTICK=1 for TrackPoint scrolling to work, and also for the AttrTrackpointMultiplier quirk to apply in libinput (otherwise the TrackPoint is too slooooow).
2019-03-11 07:00:03 +08:00
ID_INPUT_POINTINGSTICK=1
hwdb: Force "mouse" type on Logitech Ultrathin Touch Mouse Closes: #15657
2020-05-05 22:38:37 +08:00
hwdb: Fix Logitech G915 TKL (Bluetooth) appearing as a mouse
2024-06-23 03:25:21 +08:00
# Logitech G915 TKL Keyboard (Bluetooth)
id-input:modalias:input:b0005v046DpB35Fe0022*
ID_INPUT_MOUSE=0
hwdb: Force "mouse" type on Logitech Ultrathin Touch Mouse Closes: #15657
2020-05-05 22:38:37 +08:00
# Logitech Ultrathin Touch Mouse
Partially revert "hwdb: add trailing ":*" everywhere" This reverts commit c0443b97b71d5f70a0622061f589307bec5502c6. I got various cases wrong: "usb:v04F3p2B7Cd5912dc00dsc00dp00ic03isc00ip00in00" "usb:v0627p0001:QEMU USB Tablet" "input:b0003v0627p0001e0001-e0,1,2,4,k110,111,112,r0,1,8,B,am4,lsfw" OTOH: -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* is OK. Other parts follow after 'pn'. -mouse:*:name:*Trackball*:* -mouse:*:name:*trackball*:* -mouse:*:name:*TrackBall*:* +mouse:*:name:*Trackball*: +mouse:*:name:*trackball*: +mouse:*:name:*TrackBall*: ... and anything else with :name should be OK too, because our imports always include ":" at the end: IMPORT{builtin}="hwdb 'joystick:$env{ID_BUS}:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'" Including '*' at the end makes the pattern work even if we decide to add something to the match string later. Fixes #17499.
2020-11-03 21:17:53 +08:00
id-input:modalias:input:b0005v046DpB00De0700*
hwdb: Force "mouse" type on Logitech Ultrathin Touch Mouse Closes: #15657
2020-05-05 22:38:37 +08:00
ID_INPUT_MOUSE=1
hwdb: Force no "mouse" type on Logitech MX Keys Fixes https://gitlab.freedesktop.org/upower/upower/-/issues/128
2021-01-07 16:14:16 +08:00
# Logitech MX Keys
id-input:modalias:input:b0003v046Dp408Ae0111*
hwdb: CH Pro Pedals not classified correctly due to no buttons
2022-01-20 11:38:21 +08:00
ID_INPUT_MOUSE=0
hwdb: treat logitech craft keyboard as a keyboard
2022-01-28 05:08:30 +08:00
# Logitech Craft Keyboard
id-input:modalias:input:b0003v046Dp4066e0111*
ID_INPUT_MOUSE=0
hwdb: CH Pro Pedals not classified correctly due to no buttons
2022-01-20 11:38:21 +08:00
# CH Products Pro Pedals
hwdb: Remove version check in CH Pro Pedals rule CH Pedals are incorrectly reported as an accelerometer [1], because they have no button. This is fixed by a rule in 60-input-id.hwdb [2], but the rule checks id/version="0100", while my pedals report id/version="0111". So there are several versions of the pedals, presumably all affected by the bug. Remove the version check in the rule to fix them all. [1] https://bugs.freedesktop.org/show_bug.cgi?id=81889 [2] commit: 230ed4c4ba (hwdb: CH Pro Pedals not classified correctly due to no buttons, 2022-01-19) PR: https://github.com/systemd/systemd/pull/22184
2024-02-16 03:23:49 +08:00
id-input:modalias:input:b0003v068Ep00F2*
hwdb: CH Pro Pedals not classified correctly due to no buttons
2022-01-20 11:38:21 +08:00
ID_INPUT_ACCELEROMETER=0
ID_INPUT_JOYSTICK=1
Update 60-input-id.hwdb: add TEX Shinobi (#29068) * Update 60-input-id.hwdb: add TEX Shinobi The TEX Shinobi keyboard with trackpoint incorrectly identifies as a mouse instead of a pointing stick. This corrects it as suggested at https://gitlab.freedesktop.org/libinput/libinput/-/issues/932#note_2069967 Following the example of the Lite-On keyboard entry, this modalias specifies the mouse unit without tagging the device's other entries.
2023-09-06 16:59:19 +08:00
# TEX Shinobi Trackpoint
id-input:modalias:input:b0003v04D9p0407e0111-e0,1,2,4*
ID_INPUT_POINTINGSTICK=1
hwdb: ASRock LED Controller classified incorrectly as joystick due to buttons and axis (#32775) The function `builtin-input_id` incorrectly identifies the ASRock LED Controller as an input device due to the presence of buttons and axis. To fix this we add a new rule in `hwdb.d/60-input-id.hwdb`. The properties have been set to empty instead of `0` because some programs might check if the value is set at all instead of checking its value, as discussed in #32773. The device has no real keys. The devices is controlled by i2c interface and some settings in UEFI, and it provides an header to connect LED strips and similar devices. I suppose it's possible that ASRock intended to connect devices with buttons for controlling LEDs to it, but: (i) the controller itself does not have key, (ii) to my knowledge no such device exists. So I think we can unset that property as well. On a sidenote, unsetting those properties does not affect the i2c interface, OpenRGB still interacts normally with the device. Fixes #32773.
2024-05-13 21:49:07 +08:00
# ASRock LED Controller
id-input:modalias:input:b0003v26CEp01A2*
ID_INPUT_JOYSTICK=
ID_INPUT_KEY=
ID_INPUT=
Reference in New Issue Copy Permalink