*frames per urb
* *lengths of valid data
* *length of mess
*
16
27520
4472
But you said this was at 2 KB/uframe high bandwidth rate, so that math doesn't check out: 16 frames/urb * 8 uframes/frame * 2 KB/uframe means 256 KByte/urb, not 128 bytes shy of 27 KB. And if you meant 16 uframes per urb, 27 KB takes almost 14 uframes, not 16.
Because patterns of valid and invalid data are very regular, I think that it may be a bug in itd sheduling.
Or maybe the buffer overflow (into next page) logic filling up the ITDs, given the other cases were exactly one or two packets. You might have a look at that part of the code. Or maybe you can just post a way for someone else to reproduce the problem ... :)
- Dave
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
