summaryrefslogtreecommitdiff
path: root/rules/rules.d/60-persistent-input.rules
AgeCommit message (Collapse)Author
2011-08-05implement path_id, usb_id, input_id as built-in commandKay Sievers
2011-08-04rules: move input_id to default rulesKay Sievers
On Tue, Aug 2, 2011 at 10:56, Thomas Bächler <thomas@archlinux.org> wrote: > Commit c49df20758e0f22778cfc93b598f2929f4c86272 prevented udev from > creating broken symlinks for bluetooth hid devices. Unfortunately, > it also removed the ID_INPUT=1 and ID_INPUT_{KEY,MOUSE}=1 properties > from those devices. Xorg relies on these properties for cold- and > hotplugging of input devices.
2011-07-20rules: input - do not create (broken) links for bluetooth devicesKay Sievers
2011-07-10rules: input - call path_id for ACPI devicesKay Sievers
2011-06-06rules: run input_id for main input devices tooKay Sievers
2011-02-1560-persistent-input.rules: Do not create duplicate linksMartin Pitt
Commit 5e9eb156c added new symlinks for multi-interface USB input devices. However, we do not actually need the one for interface number "00", as we already have the symlink without the interface number.
2011-02-1560-persistent-input.rules: Support multiple interfacesMartin Pitt
Create /dev/input/by-id symlinks containing the USB interface number so that each interface in a multi-interface USB input device gets its own symlink. Thanks to a7x <ubuntu-a7x@scientician.org>! https://launchpad.net/bugs/626449
2010-04-12replace "add|change" with "!remove"Kay Sievers
2010-03-16rules: input - create by-path/ links for pci devicesMarco d'Itri
2009-11-30input: Deprecate ENV{ID_CLASS}Martin Pitt
The ID_CLASS property on input devices has been replaced by the more accurate set of flags ID_INPUT_{KEYBOARD,KEYS,MOUSE,TOUCHPAD,TABLET,JOYSTICK}. Rewrite 60-persistent-input.rules to use the new properties now and not export ID_CLASS any more, since it is not used by anything else any more. Add note about migration to NEWS, in case this is being used in custom rules.
2009-11-30extras: Add input_idMartin Pitt
input_id probes input/event devices for their class (keyboard, keys, mouse, touchpad, tablet, joystick). This is based on the corresponding hal code in hald/linux/device.c, input_test_{abs,rel,...}. This should provide enough functionality to get hal-less X.org working (which in particular needs to know exactly which devices are touchpads). Replace the brittle hacks in 60-persistent-input.rules with checking for the new ID_INPUT_* flags. This keeps the old ID_CLASS properties for now (but they are to be removed later on). Note: The current code has several hacks still, which are to be replaced with proper libudev calls later on.
2009-08-05rules: exclude digitizers from joystick classAnssi Hannula
Exclude digitizers and similar devices from ID_CLASS joystick by checking modalias for BTN_DIGI. This was also done for linux kernel joydev interface in linux commit d07a9cba6be5c0e947afc1014b5a62182a86f1f1.
2009-06-04rules: do not call path_id for virtual devicesKay Sievers
2009-05-01rules: add "event*" matchKay Sievers
2009-04-27rules: input - fix commentsKay Sievers
2009-04-27rules: input - add links for USB/platform non-kbd/mouse devicesKay Sievers
2009-02-26usb_id: add ID_USB_INTERFACES=:0e0100:0e0200:010100:010200:Kay Sievers
2009-01-02rules: input - make sure needed variables are setKay Sievers
2008-08-29libudev: require LIBUDEV_I_KNOW_THE_API_IS_SUBJECT_TO_CHANGEKay Sievers
2008-07-18move default rules from /etc/udev/rules.d/ to /lib/udev/rules.d/Kay Sievers
None of these rules is supposed to be changed by users, so move them out of /etc. Custom rules, and automatically generated rules stay in /etc. All rules are still processed in lexical order, regardless which directory they live in.