2017-06-26 12:17:36 +02:00
|
|
|
# This file is part of systemd.
|
|
|
|
|
#
|
|
|
|
|
# Database for joystick device information that cannot be queried directly.
|
|
|
|
|
#
|
|
|
|
|
# The lookup keys are composed in:
|
|
|
|
|
# 70-joystick.rules
|
|
|
|
|
#
|
|
|
|
|
# Note: The format of the "joystick:" 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.
|
|
|
|
|
#
|
|
|
|
|
# Match string format:
|
|
|
|
|
# joystick:<bustype>:v<vid>p<pid>:name:<name>:
|
|
|
|
|
#
|
|
|
|
|
# vid/pid as 4-digit hex lowercase vendor/product
|
|
|
|
|
#
|
|
|
|
|
# To add local entries, create a new file
|
|
|
|
|
# /etc/udev/hwdb.d/71-joystick-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 joystick 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.
|
|
|
|
|
#
|
|
|
|
|
# Permitted keys:
|
|
|
|
|
# Specify if a joystick is a built-in one or external:
|
|
|
|
|
# ID_INPUT_JOYSTICK_INTEGRATION=internal|external
|
|
|
|
|
#
|
|
|
|
|
# If the property is missing, user-space can assume:
|
|
|
|
|
# ID_INPUT_JOYSTICK_INTEGRATION=external
|
2020-10-15 09:22:35 +02:00
|
|
|
#
|
|
|
|
|
# All matches should end in ':*' to allow future expansions of the match key.
|
2017-06-26 12:17:36 +02:00
|
|
|
|
|
|
|
|
joystick:bluetooth:*
|
|
|
|
|
ID_INPUT_JOYSTICK_INTEGRATION=external
|
|
|
|
|
|
|
|
|
|
###########################################################
|
|
|
|
|
# GPD
|
|
|
|
|
###########################################################
|
|
|
|
|
|
|
|
|
|
# GPD Win, Classic and XBox 360 compat modes
|
hwdb: add trailing ":*" everywhere
No functional change is intended.
The general pattern of changes:
-usb:v04F3p2B7C*
+usb:v04F3p2B7C:*
This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY
part visually separated. It would only make a difference if we added further
keys with a different number of digits, which is unlikely.
-usb:v0627p0001:*QEMU USB Keyboard*
-usb:v0627p0001:*QEMU USB Mouse*
-usb:v0627p0001:*QEMU USB Tablet*
+usb:v0627p0001:*QEMU USB Keyboard*:*
+usb:v0627p0001:*QEMU USB Mouse*:*
+usb:v0627p0001:*QEMU USB Tablet*:*
Again, only a clarification. We know that ":" will appear somewhere later in
the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*".
-evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV*
+evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:*
This makes the match narrower. Previously we would match product "N53SV"
and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must
match exactly. Most of the changes in this patch match this pattern. I made a few
judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included:
-evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*
+evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:*
-evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:
+evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:*
This more like the "QEMU" example above, since all dmi strings end in ":", so
anything which matches the old version will also match the new version.
-evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr*
+evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:*
I replaced trailing ":pvr*" by ":*". This makes no functional difference because
we expect "pvr" to always appear in the dmi string. This makes patterns shorter.
-evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*
+evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:*
OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we
skip it, we should make it clear that this is on purpose, that we really want to
match any product name.
The python script to generate autosuspend rules is updated to use ":*" too.
Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
2020-10-15 09:23:30 +02:00
|
|
|
joystick:usb:v11c5p5507:*
|
|
|
|
|
joystick:usb:v045ep028e:*
|
2017-06-26 12:17:36 +02:00
|
|
|
ID_INPUT_JOYSTICK_INTEGRATION=internal
|