Randy.Dunlap wrote:
> Do you have a USB protocol analyzer so that you can see what the
> device and bus are doing? You know that the device is stalling
> on this request (get string index = 100)?
Fortunately the USB device is also under my control, so theres no need
to dig out the protocol anal
On Tue, 11 Jun 2002, Svein E. Seldal wrote:
| Randy.Dunlap wrote:
| > On Tue, 11 Jun 2002, Svein E. Seldal wrote:
| >
| > | 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
Randy.Dunlap wrote:
> On Tue, 11 Jun 2002, Svein E. Seldal wrote:
>
> | 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
>
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 shoul
