5 Commits

Author	SHA1	Message	Date
Simon Arlott	6fcae8e4de	rules: run all persistent-input rules for rmi and i8042 (#7287) ... Commit 83b48159 set ID_BUS for these subsystems but copied the intent of commit c49df207 by not creating symlinks for those devices. Remove the GOTO so that the rest of the rules are still processed and symlinks are created for rmi and i8042 devices.	2017-11-10 10:32:51 +01:00
Peter Hutterer	f013e99e16	rules: set ID_BUS=bluetooth for any device with id/bustype attr of 0x0005 (#5539) ... Not all bluetooth devices come through the bluetooth subsystem and those that don't currently lack the ID_BUS=bluetooth env. This again fails to apply udev rules and/or hwdb entries that rely on the bluetooth bustype to be set. Fix this by checking the attribute id/bustype on the device instead of just the subsystem. Fixes #4566	2017-03-07 07:55:58 +01:00
Peter Hutterer	83b481599b	rules: set ID_BUS for bluetooth, rmi and i8042 ... Something has to so we can have udev rules rely on this. Right now the ID_BUS setting is inconsistent: usb is set, ata and pci are set, bluetooth is not set, rmi is too new to be featured. 70-mouse even relied on bluetooth even though it was never set	2016-07-01 15:19:46 +10:00
Martin Pitt	fb5d873cfd	rules: Fix persistent input symlinks for interface 00 ... Commits 5e9eb156c and 32567f8 introduced persistent symlinks for input devices with more than one interface. However, this does not ensure stability for the "default" interface, i. e. with interface number 00 or a nonexisting one. If a device with a higher interface number appears first, it'll claim the symlink name without an interface number, and the "interface 00" device won't get any. Fix this by creating the default symlink only for interface 00 or a nonexisting one, so that we properly partition the two cases over the two rules. https://launchpad.net/bugs/1057824	2012-10-11 08:21:17 +02:00
Kay Sievers	3e2147858f	move imported udev into place	2012-04-04 05:05:07 +02:00