On Thu, 2002-01-03 at 14:26, Greg KH wrote: > On Thu, Jan 03, 2002 at 02:08:58PM -0700, Gordon McNutt wrote: > > > > However, I'm convinced that the toggle bit should be advanced if and > > only if the packet was ACKd. Advancing it on a NAK seems to defeat the > > whole purpose of the toggle mechanism as a means of keeping the host and > > peripheral in synch. > > I think you are correct. According to the USB spec, in section 8.6 it > says: > Transmitter sequence bits toggle only when the data transmitter > receives a valid ACK handshake. > > So it looks like a bug in the host controller driver. Does the same > thing happen for usb-uhci.o or usb-ohci.o? >
I can make this happen 100% of the time with usb-uhci.o 2.4.17. I expect other devices would see this as well, but if their class drivers persist in resending NAKd packets (or reset the peripheral if a timeout occurs) then they may never encounter this problem. With uhci.o 2.4.17 I have the completely different problem where the peripheral never responds to the packet (no ACK, no NAK, no STALL... nothing). I'm stumped by that... all I do is change the host controller driver -- but this seems like a symptom of a peripheral problem. No Clue. Regards, --gmcnutt _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
