2006/3/17, Pete Zaitcev <[EMAIL PROTECTED]>:
> On Fri, 17 Mar 2006 10:54:25 +0100, "Franck Bui-Huu" <[EMAIL PROTECTED]>
> wrote:
>
> >[...]
> > I'm suprised to see that for the first IN token asking for 36 data
> > bytes, the host actually received the answer of the second IN token
> > which is 13 bytes long; specially that I previously checked with an
> > USB analyzer that the data correctly transited on the bus...
> > I joined a screenshot of the USB analyzer capturing the traffic for
> > the second plug.
>
> I am just guessing, but what if something is not right with the toggle?
> It should be easy to prove by reducing the maxpacket and thus breaking
> the inquiry data in two. If you have a moment, please try to plug the
> device into a 1.1 hub. Then if the data IN for 36 bytes gets 4 bytes
> instead of 13, we have the problem... Maybe input and output toggles
> got confused.
>
your guess is right, I've found it too by sparing the analyzer's trace
better. The device was indeed sending a DATA1 PID instead of a DATA0
one. Sorry for the noise...
Thanks
--
Franck
-------------------------------------------------------
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&kid0944&bid$1720&dat1642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
