On Wed, 4 Oct 2006 [EMAIL PROTECTED] wrote: > Hi Alan, > > I've gathered a few example traces here: ... > The traces were all made without a hub. > > What's interesting to see is that for most failed requests the first data > transaction follows within less than 500 microseconds after the SETUP > transaction. It's not always the case, but it definitely seems to help > trigger the problem.
The same thing is true for most of the successful transfers as well, so I'm not sure what to make of it. Incidentally, the trace shows that quite often the device responding to PING with ACK even though it's not ready to accept any data. That happens lots and lots of times. It looks like another bug. The same sort of thing happens with those failed commands. There's a long period where the devices waffles back and forth, sometimes sending ACK, sometimes NAK, until eventually it sends STALL. Why doesn't it send STALL right away if it thinks the protocol has been violated? The real question is why does the device work under Windows. To answer that will require looking at traces made with a Windows host. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
