From: Greg KH <gregkh@suse.de>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Adrian Bunk <bunk@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Oliver Neukum <oneukum@suse.de>,
Matthew Dharm <mdharm-usb@one-eyed-alien.net>
Subject: Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6
Date: Fri, 14 Sep 2007 02:59:00 -0700 [thread overview]
Message-ID: <20070914095900.GA19032@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0709141047580.24429@twin.jikos.cz>
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
next prev parent reply other threads:[~2007-09-14 9:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 13:33 [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6 Greg KH
2007-09-13 14:52 ` Adrian Bunk
2007-09-13 15:20 ` Alan Stern
2007-09-13 15:40 ` Adrian Bunk
2007-09-13 16:07 ` Alan Stern
2007-09-13 16:34 ` Greg KH
2007-09-13 16:43 ` Linus Torvalds
2007-09-13 19:13 ` Alan Stern
2007-09-14 0:24 ` Matthew Dharm
2007-09-14 14:34 ` Alan Stern
2007-09-14 8:55 ` Jiri Kosina
2007-09-14 9:59 ` Greg KH [this message]
2007-09-13 19:26 ` Pete Zaitcev
2007-09-13 20:19 ` Adrian Bunk
2007-09-13 20:31 ` Alan Stern
2007-09-13 20:44 ` Linus Torvalds
2007-09-13 21:28 ` Adrian Bunk
2007-09-13 22:05 ` Adrian Bunk
2007-09-14 0:11 ` Linus Torvalds
2007-09-14 13:21 ` Mark Lord
2007-09-14 14:15 ` Adrian Bunk
2007-09-14 14:29 ` Alan Stern
2007-09-14 14:26 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2007-09-17 12:56 Hans de Goede
2007-09-18 10:39 Joerg Schilling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070914095900.GA19032@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=oneukum@suse.de \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox