Hi all,
I have a report here of a device in the wild that is using a USB vendor
id of 0x0000. From everything I can tell, this _could_ be a valid
vendor id, but I'm pretty sure that it isn't :)
Here's the bug report, does anyone have an idea of what we should do
here?
At first glance, we should probably fix the scripts/mod/file2alias.c
code that does the following in do_usb_entry_multi():
/*
* Some modules (visor) have empty slots as placeholder for
* run-time specification that results in catch-all alias
*/
if (!(id->idVendor | id->bDeviceClass | id->bInterfaceClass))
return;
And check both that idVendor and idProduct are 0x0000 before falling out.
Does anyone see a problem with that?
thanks,
greg k-h
----- Forwarded message from Janusz <[EMAIL PROTECTED]> -----
Date: Fri, 11 Jan 2008 12:27:42 +0100
From: Janusz <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: USB VendorID=0x0000
Hello !
I'd like kindly ask to help me with modyfiying USB driver for the LCD display
avaialbe with GMC chassis. The problem I have (and I think the biggest) is
that device is presented on USB bus as: vendorid=0x0000, productid=0xff02.
Macro USB_DEVICE strips 0x0000 from MODULE_DEVICE_TABLE and kernel doesn't
recognize this device (it isn't exported to modules.usbmap, too).
Could you tell me that to do with it (on M$ it works !) ?
Maybe some temporary fix ...
Thanks in advance and best regards
Janusz
----------------------------------------------------------------------
Stworz najlepsza modelke na swiecie!
Sprawdz >>> http://link.interia.pl/f1cc4
----- End forwarded message -----
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
