[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070914095900.GA19032@suse.de>
Date: Fri, 14 Sep 2007 02:59:00 -0700
From: Greg KH <gregkh@...e.de>
To: Jiri Kosina <jikos@...os.cz>
Cc: Alan Stern <stern@...land.harvard.edu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Adrian Bunk <bunk@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Kernel development list <linux-kernel@...r.kernel.org>,
USB development list <linux-usb-devel@...ts.sourceforge.net>,
Oliver Neukum <oneukum@...e.de>,
Matthew Dharm <mdharm-usb@...-eyed-alien.net>
Subject: Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6
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 majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists