| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Commit 2b463cb0 changed the rules to match against hiddev* for all devices in
an attempt to fix Debian #567237/LP #444420. However, this caused regressions
with other devices (e. g. LP #550288) and thus was reverted in commit 8b56ba.
Now use hidraw* for the devices where it's confirmed that they only work with
that, and hiddev* for the others.
https://launchpad.net/bugs/444420
|
|
|
|
This reverts commit 2b463cb050cbf77d9c6b51e0f5a9d89bf7eb1bc3.
|
|
|
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567237
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/444420
|
|
For the retrigger of the device on remove we were trying to match bmAttributes
of self powered which is unnecessary.
|
|
|
|
|
|
|
|
We must never access random devices in /dev which do not belong to
the event we are handling. Hard-coding /dev/hidrawX, and looping over all
devices is absolutely not acceptable --> hook into hidraw events.
We can not relay on (rather random) properties merged into the parent
device by earlier rules --> use libudev to find the sibling device
with a matching interface.
Libusb does not fit into udev's use case. We never want want to scan
and open() all usb devices in the system, just to find the device
we are already handling the event for --> put all the stupid scanning
into a single function and prepare for a fixed libusb or drop it later.
|
|
|
|
|
|
The previous rules just checked bInterfaceProtocol but not the actual device
and interface class. This caused the hci rules to be applied for Dell USB hubs
and attached input devices like keyboards and mouses as well, breaking them
completely.
Tighten the match to also check device and interface class/subclass.
https://launchpad.net/bugs/392144
|
|
|
|
|
