Hi,
I think the beginning of the transaction is that 8 byte setup TD, which already reset to DATA0. The (optional) follow up data TD start at the second TD, (if any). Since they are pointed by the same ED, I guess the data TD should be able to using toggle bit, which was reseted by the first setup TD?
With all the different versions of OHCI silicon around, this is a case where I'd say "better safe than sorry". That may just be paranoia, but on the other hand we _know_ all the current "works with Linux" silicon works with DATA1 there today, and there's no need to change it.
Should I force to reset the first data TD (which is the second TD in the whole transaction) to use DATA1 then do toggle for the rest of data TD?
That's how I'd do it -- so your update is only to support more data stage TDs, not in how the first (and usually only) one of them gets initialized. - Dave ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
