On Thu, Jan 03, 2002, Greg KH <[EMAIL PROTECTED]> 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?
Sorry for the delayed reponse. This is highly unlikely. The way UHCI works, you pre setup the data toggle in the TD's and the UHCI controller does the rest. It does not advance to the next TD if it receives a NAK. For what you described to happen, usb-uhci.c would need to scan the TD's, find the TD which is being NAK'd and then retoggle that TD and all of the following TD's, which is something that just doesn't happen by accident and would be very difficult since we don't get interrupts on NAK's. Do you have a CATC trace that we can take a look at? JE _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
