On Fri, Sep 14, 2007 at 10:55:46AM +0200, Jiri Kosina wrote: > For the rest of the HID quirks -- most of them are also workarounds for > broken classess of devices. Usually, they claim to be HID-compliant device > in their file descriptor, but they do not follow the spec (they send > inverted axes values, send usage codes that violate the specification, > etc), but we can easily work around these bugs by a few lines of code and > let the devices to be handled by usbhid flawlessly. I guess this is worth > it.
The reason for this is that the only way to write a userspace "driver" for USB devices on Windows versions prior to Vista was to be a HID device. Your userspace program could then easily grab the device and control it. This could be fixed in Linux by providing a way to have driver "heirachy" for USB whereby a vendor/product id providing driver would take a higher priority than a class driver. But we've been talking about that for over 7 years now :) thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
