Vladimir Dergachev wrote: > > The problem is like this: (if you remember I using FX2 device): > UHCI part works fine. EHCI does not.
Are you still hooking the FX2 chip directly to the bus? I'm not sure that's expected to work at high speed. It's been ages since I did anything with circuit designs but I do know that the USB2 highspeed signal paths are tricky. > here is part of the log: > > ------------------------------------------------------------------------ > hub.c: USB new device connect on bus4/4, assigned device number 2 > usb.c: USB device not responding, giving up (error=-71) > hub.c: USB new device connect on bus4/4, assigned device number 3 > usb.c: USB device 3 (vend/prod 0x4b4/0x8613) is not claimed by any active > driver > . > usb.c: USB disconnect on device 3 > hub.c: USB new device connect on bus4/4, assigned device number 4 > usb.c: USB device not responding, giving up (error=-71) > hub.c: USB new device connect on bus4/4, assigned device number 5 > usb.c: USB device not responding, giving up (error=-71) > hub.c: USB new device connect on bus4/4, assigned device number 6 > usb.c: USB device 6 (vend/prod 0x4b4/0x8613) is not claimed by any active > driver > . > usb.c: USB disconnect on device 6 > hub.c: USB new device connect on bus4/4, assigned device number 7 > usb.c: USB device not responding, giving up (error=-71) > hub.c: USB new device connect on bus4/4, assigned device number 8 > usb.c: USB device not responding, giving up (error=-71) > --------------------------------------------------------------------------- > > So, basically, it connects fine to UHCI part and then fails to switch over > to EHCI. I'm not sure that's what I see. 71 == EPROTO ... but if bus4 is the EHCI bus, then it enumerated twice, but then disconnected. The EHCI code returns EPROTO in several cases. From looking at the current code: - Missed Micro Frame error, for split transaction (not your situation) - "three strikes" ... three timeout, crc, or pid errors consecutively (maybe you're seeing this) - grab-bag error, no specific status available (maybe) - ISO transaction error (not your case) You could figure out which EPROTO case you're hitting by enabling the debug messages. - Dave _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
