Bug 15885

Summary:	usbtouchscreen alias list is bad
Product:	Drivers	Reporter:	Daniel Skorka (skorka)
Component:	USB	Assignee:	Greg Kroah-Hartman (greg)
Status:	RESOLVED INVALID
Severity:	low
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	2.6.26-2	Subsystem:
Regression:	No	Bisected commit-id:

Description Daniel Skorka 2010-04-30 16:06:45 UTC

The alias list in driver usbtouchscreen contains several entries with vendor ID 0x1234. As far as I can make out, this ID has not been assigned to anyone, but seems to be in use in several devices being sold. I have found a MP3 player using vendor 0x1234 and product 0x5678, which is one of the entries. This entry in usbtouchscreen prevents the usb_storage driver from driving the device, which it would otherwise do, due to the information in the device descriptor. A workaround by using /etc/modprobe.d/ is necessary to get the correct driver to handle the player. I therefore suggest dropping those entries, or at least, if possible, that usbtouchscreen reads the descriptor to find out if it really can drive the device, and if not, hands it over so the other drivers can have a go at it.

Comment 1 Greg Kroah-Hartman 2010-04-30 16:14:41 UTC

On Fri, Apr 30, 2010 at 04:06:50PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> The alias list in driver usbtouchscreen contains several entries with vendor
> ID
> 0x1234.

That is because it is needed for some devices.

> As far as I can make out, this ID has not been assigned to anyone, but
> seems to be in use in several devices being sold. I have found a MP3 player
> using vendor 0x1234 and product 0x5678, which is one of the entries. This
> entry
> in usbtouchscreen prevents the usb_storage driver from driving the device,
> which it would otherwise do, due to the information in the device descriptor.

That is a bug, please bring it up on the linux-usb@vger.kernel.org
mailing list.

Comment 2 Greg Kroah-Hartman 2012-02-22 21:12:54 UTC

All USB bugs should be sent to the linux-usb@vger.kernel.org mailing 
list, and not entered into bugzilla.  Please bring this issue up there,
if it is still a problem in the latest kernel release.