On Mon, 3 Jun 2002, David Brownell wrote:
> > 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.
That could certainly be the case, but I have no problems with NEC
controller, so I'll ignore this for now (as I don't have equipment to test
this anyway) and hope someone else stumbles on the same issue.
thanks for your help
Vladimir Dergachev
>
> - 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
