Vladimir Dergachev wrote: > > Here is the log with DEBUG enabled. I have tried putting in a longish > delay just before dbg( "3strikes" ) and it produces the same log, so it is > likely not a power issue after all.
Signal quality problems are still an option ... I've seen the FX2 protoboard work OK with VIA-based adapters. I recall hearing that getting devices to enumerate at both full and high speeds wasn't always straightforward. > ehci-hub.c: GetStatus port 1 status 0x1803 POWER speed=2 CSC CONNECT > ehci-hub.c: 00:0b.2 port 1 full speed, give to companion, 0x1801 > ehci-hub.c: GetStatus port 1 status 0x3801 OWNER POWER speed=2 CONNECT > ehci-hcd.c: 00:0b.2: free_config devnum 0 > ehci-hub.c: GetStatus port 4 status 0x1803 POWER speed=2 CSC CONNECT > ehci-hub.c: 00:0b.2 port 4 high speed > ehci-hub.c: GetStatus port 4 status 0x1005 POWER speed=0 PE CONNECT So far so good -- the "chirp" did its bit. > hub.c: USB new device connect on bus4/4, assigned device number 2 > ehci-q.c: 3strikes > ehci-q.c: ep 0-in qtd token 00080248 --> status -71 [ repeats ] Token value translates as an 8 byte SETUP packet that halted because of three consecutive transaction errors ... like CRC error, timeout, or bad PID (like a NAK or NYET response). Bad signaling could cause CRC and timeout errors, I think. - 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
