~lukeshu/systemd - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2009-08-07	hid2hci: install re-trigger for hid device when recovering from S3	Mario Limonciello

2009-07-24	hid2hci: rewrite (and break) rules and device handling	Kay Sievers
	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.
2009-07-22	hid2hci: support to hid2hci for recovering Dell BT devices after S3	Mario Limonciello

2009-06-26	hid2hci: narrow matches to real HCI devices	Martin Pitt
	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
2009-06-16	hid2hci: move from udev-extras	Mario Limonciello