On Sat, Jun 26, 2004 at 11:50:58AM -0400, Alan Stern wrote:
> On Sat, 26 Jun 2004, Tommy Faasen wrote:
>
> > Alan Stern wrote:
> >
> > thanks for the explenation
> >
> > >
> > >Come to think of it, I told you to increase the time delay before the
> > >usb_get_device_descriptor() call. But that comes _after_ the call to
> > >hub_set_address(), which is the one that's failing. Maybe you should try
> > >adding a line that says
> > >
> > > msleep(100);
> > >
> > >(or perhaps a longer delay -- you can try 1000 or even higher) immediately
> > >before the call to hub_set_address().
> > >
> > >
> > >
> > In the code I added msleep(1000) like this
> >
> > for (i = 0; i < GET_DESCRIPTOR_TRIES; ++i) {
> > usb_get_descriptor_broken(udev);
> > msleep(200);
> > for (j = 0; j < SET_ADDRESS_TRIES; ++j) {
> > msleep(1000);
> > retval = hub_set_address(udev);
> > if (retval >= 0)
> > break;
> > msleep(200);
> > }
> >
> > Unfortunatley, Still no luck
> >
> > usb 1-2: new full speed USB device using address 3
> > uhci_hcd 0000:00:07.2: uhci_result_control: failed with status 440000
> > [dbeb6240] link (1beb61e2) element (1bea1040)
> > 0: [dbea1040] link (1bea1080) e0 Stalled CRC/Timeo Length=7 MaxLen=7
> > DT0 EndPt=0 Dev=0, PID=2d(SETUP) (buf=1e3b8568)
> > 1: [dbea1080] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1
> > EndPt=0 Dev=0, PID=69(IN) (buf=00000000)
>
> Now that's strange. The failing message is the Set-Address. (You can
> tell because it has a Setup stage and a Status stage but no Data stage.)
> This means that the Get-Descriptor message sent by
> usb_get_descriptor_broken() succeeded! For some reason this device just
> doesn't like to respond to those Set-Address messages. Maybe it is unable
> to use certain addresses?
That seems unlikely as other uhci people have reported no problems and
on my other system everything seems to be ok as well.
I think it's a combination of the VIA kt133a chipset and this device.
> You could try changing SET_CONFIG_TRIES
> (defined elsewhere in hub.c) to something larger, like 10 or 20. Each of
> those iterations uses a different address.
>
I'have a go when I get back home, monday or so...
> Basically I have no idea what's going on with your device. Is there any
> hope of getting some technical information from the manufacturer?
>
I don't know, it seems it was released sort of by accident... and later
on pulled from the sweex website?
I'll give it a try anyway....
Tommy
> Alan Stern
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
