mirror of
https://github.com/systemd/systemd
synced 2024-07-05 17:39:42 +00:00
1642b7b3ac
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.
88 lines
2.6 KiB
Plaintext
88 lines
2.6 KiB
Plaintext
# This file is part of systemd.
|
|
#
|
|
# The lookup keys are composed in:
|
|
# 60-input-id.rules
|
|
#
|
|
# Match string formats:
|
|
# id-input:modalias:<modalias>
|
|
#
|
|
# 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
|
|
# 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.
|
|
#
|
|
# Allowed properties are:
|
|
# 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
|
|
#
|
|
# 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
|
|
#
|
|
# Allowed values are 1 and 0 to set or unset, respectively.
|
|
#
|
|
# NOT allowed in this file are:
|
|
# ID_INPUT_WIDTH_MM, ID_INPUT_HEIGHT_MM, ID_INPUT_TOUCHPAD_INTEGRATION
|
|
#
|
|
|
|
# Example:
|
|
# id-input:modalias:input:b0003v1234pABCD*
|
|
# ID_INPUT_TOUCHPAD=1
|
|
# ID_INPUT=1
|
|
|
|
# Sort by brand, model
|
|
|
|
# XP-PEN STAR 06
|
|
id-input:modalias:input:b0003v28bdp0078*
|
|
ID_INPUT_TABLET=1
|
|
|
|
# Lite-On Tech IBM USB Travel Keyboard with Ultra Nav Mouse
|
|
id-input:modalias:input:b0003v04B3p301Ee0100-e0,1,2,4*
|
|
ID_INPUT_POINTINGSTICK=1
|
|
|
|
# Logitech Ultrathin Touch Mouse
|
|
id-input:modalias:input:b0005v046DpB00De0700*
|
|
ID_INPUT_MOUSE=1
|
|
|
|
# Logitech MX Keys
|
|
id-input:modalias:input:b0003v046Dp408Ae0111*
|
|
ID_INPUT_MOUSE=0
|
|
|
|
# Logitech Craft Keyboard
|
|
id-input:modalias:input:b0003v046Dp4066e0111*
|
|
ID_INPUT_MOUSE=0
|
|
|
|
# CH Products Pro Pedals
|
|
id-input:modalias:input:b0003v068Ep00F2*
|
|
ID_INPUT_ACCELEROMETER=0
|
|
ID_INPUT_JOYSTICK=1
|
|
|
|
# TEX Shinobi Trackpoint
|
|
id-input:modalias:input:b0003v04D9p0407e0111-e0,1,2,4*
|
|
ID_INPUT_POINTINGSTICK=1
|
|
|
|
# ASRock LED Controller
|
|
id-input:modalias:input:b0003v26CEp01A2*
|
|
ID_INPUT_JOYSTICK=
|
|
ID_INPUT_KEY=
|
|
ID_INPUT=
|