On Sat, 4 Sep 2004, Steve Calfee wrote: > One thing to keep in mind while looking at these traces is that windows > cannot respond to any I/O event in a couple of milliseconds. Therefore in > the initial get device descriptors you see the setup packet, a few frames > pause where the windows interrupt routine makes sure something is out there > and then the IN request for 64 (0x40) bytes followed immediately by the zero > length OUT packet completing the transaction.
It's probably not worth harping on this, but... That few frames' delay after the Setup packet isn't because a Windows interrupt routine is doing something. It's because the device takes a little while to respond to the Get-Device-Descriptor request. You can see some (but not all) of the IN packets with NAK responses in the mouse trace; apparently they've been edited out of the modem trace. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
