On Thu, 3 Aug 2006, Jared Holzman wrote: > Somewhere underneath all that sarcasm,
Sorry. I sometimes get carried away. > I believe that you're saying that > the device is violating the size of the isochronous packets. From my > point of view this means that the packets are too small as I am > interested in getting the device to work, not in fixing its, possibly > broken, USB interface. > > However without a complete understanding of the USB stack, I cannot > determine if > a) The host informs the device of the sizes and offsets of the packets > to use, according to the submitted URB, and then the device is supposed > to follow them and if it doesn't you get the -EOVERFLOW? Or > b) The URB merely informs the host what size packets to expect and the > device sends what it has been configured to send and if they dont match > then the -EOVERFLOW occurs? b) is what really happens. Note that -EOVERFLOW occurs only when the actual length of the received packet is longer than what the URB has told the host to expect. If the actual length is <= the expected length then the status is 0 (no error). Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
