On Wed, Mar 01, 2006 at 07:16:26PM -0800, Pete Zaitcev wrote: > On Wed, 1 Mar 2006 18:44:11 -0800, Marc Singer <[EMAIL PROTECTED]> wrote: > > > e2372840 1612603151 C Ci:009:00 -121 32 = 09022000 0103fac0 01090400 > > 0002ff00 00fa0705 02024000 00070581 02400000 > > e2372840 1612603151 S Ci:009:00 s 80 06 0200 0000 0400 1024 < > > > So, how can this happen? Am I seeing an error in USBMON? > > I don't think usbmon (lowercase) can reorder. All buffers are circular. > > Remember that the resolution of the system clock may be lower than its > precision, so the timestamp offer only a limited guidance on some > platforms. There is no way for the URB to complete (with -EREMOTEIO) > and for usbtest to resubmit it within the same microsecond, even on > fastest PCs, but perhaps the timer just cannot distinguish such events.
I'm getting very accurate timing values, sometimes only a few microseconds different. So, if this isn't a reordering problem, then the UDC is ignoring the last request...which isn't good. What's missing is some semblence of a proper output from the USB tests. I'm looking to find out where in the conversation the UDC goes awry so that I have something to investigate. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
