summaryrefslogtreecommitdiff
path: root/udev/80-libinput-device-groups.rules.in
Commit message (Collapse)AuthorAgeFilesLines
* udev: update rules to handle bind/unbind eventsPeter Hutterer2020-11-241-1/+1
| | | | | | | | | | | | Summary: we expect add, change or remove but kernel 4.12 added bind and unbind. These events were previously discarded by udevd. Our rules should handle any event *but* remove, so update as suggested in the announce email linked below. For a longer explanation, see the system 247rc2 announcement https://lists.freedesktop.org/archives/systemd-devel/2020-November/045570.html Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* udev: don't use IMPORT+=Peter Hutterer2020-03-301-1/+1
| | | | | | | | | | | | | | | | IMPORT really only supports == and != and for a short while udevd warned about this before that warning was reverted again. Where anything else is used, it falls back to ==. systemd upstream rules all use a single = though, so let's stick with that to be consistent, even if it is technically wrong (udevd will warn about this in debug mode). See the long discussion in systemd upstream for details: https://github.com/systemd/systemd/issues/14062 Fixes #461 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* udev: directly import the device groupsPeter Hutterer2020-02-121-4/+1
| | | | | | No need for the indirection of PROGRAM, then ENV for the output value. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* udev: don't overwrite a previously set device groupPeter Hutterer2016-08-011-0/+1
| | | | | | | | In some cases a device may need a device group assigned by a custom udev rule or hwdb entry. Don't overwrite that with our generated one. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
* udev: make sure the udev callout path is valid for a test runPeter Hutterer2015-07-091-0/+8
udev requires callout binaries to sit in /lib/udev or otherwise provide an absolute path. The test suite should work without installing everything first, so create two rule files - one to install, one with the path to the $builddir/test Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>