On Tue, 11 Jun 2002, Svein E. Seldal wrote: | I have a driver that requests a specific string from an USB device, by | issuing a standard get string descriptor request (usb_string() or | usb_get_string()). | | If I ask for a invalid string, lets say index 100, the USB device stalls | (as it should), an USB exeption is printed into the syslog from the UCHI | driver, but the functions usb_string() or usb_get_string() functions | still returns 0. This leaves my driver totally unaware that the last | string request failed. Isnt this a bug?
I guess that your driver could treat a string length of 0 as an error. | Is there any ways in the driver to avoid this? What kernel version? What USB exception is logged? Can you post the log messages? I don't see a path for usb_string() or usb_get_string() to return 0 unless the device returns 0 for the string length (instead of returning an error). -- ~Randy _______________________________________________________________ Multimillion Dollar Computer Inventory Live Webcast Auctions Thru Aug. 2002 - http://www.cowanalexander.com/calendar _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
