> Yeah, I want to look at that again ... though I seem to recall > some NetChip doc saying the issue was only for IN endpoints.
I couldn't find anything in the data sheet that explicitly said this, but I did trial-and-error until I figured out what was causing problems for my 1023 byte isochronous OUT endpoint. > (Hardware couldn't add the end-of-packet bit to FIFO words in > that case, without a software-assisted "validate", but it had > no such issue with OUT packets from the host.) This seems to hold for the reverse direction as well. Hardware doesn't clear the valid bit on the descriptor if it receives a non-0-mod-4-max-sized packet. Now that I think about it again, though, it's probably only an issue for FS isochronous endpoints since they're the only ones that can even have an odd-sized MPS. > Shouldn't that happen with interrupt transfers too? Not > bulk, which only allows certain sizes; but a three byte > interrupt maxpacket is legal. Yes, you're probably right. I didn't test interrupt endpoints. > I've not really used ISO on the net2280 yet -- is it behaving > for you? Including high bandwidth modes? I was actually trying to prove that a particular 1.1 host chipset could handle max-sized ISO transfers, and I couldn't find any devices off the shelf that had max-sized ISO endpoints. All of my testing was thus FS ISO, but it would certainly be easy to plug it into my HS hub. I'll do this at some point and let you know. FS ISO worked as expected, but I didn't exactly stress it. Mostly simple loopback stuff. --Mark ------------------------------------------------------- This SF.net email is sponsored by OSDN's Audience Survey. Help shape OSDN's sites and tell us what you think. Take this five minute survey and you could win a $250 Gift Certificate. http://www.wrgsurveys.com/2003/osdntech03.php?site=8 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
