Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754675AbXINJ7U (ORCPT ); Fri, 14 Sep 2007 05:59:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750843AbXINJ7I (ORCPT ); Fri, 14 Sep 2007 05:59:08 -0400 Received: from cantor2.suse.de ([195.135.220.15]:36449 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750898AbXINJ7H (ORCPT ); Fri, 14 Sep 2007 05:59:07 -0400 Date: Fri, 14 Sep 2007 02:59:00 -0700 From: Greg KH To: Jiri Kosina Cc: Alan Stern , Linus Torvalds , Adrian Bunk , Andrew Morton , Kernel development list , USB development list , Oliver Neukum , Matthew Dharm Subject: Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6 Message-ID: <20070914095900.GA19032@suse.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1241 Lines: 28 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/