Perhaps I'm limited by the speed of my CPU, I'm only running at about 66MHz, which is half of the maximum speed of the device.
Yes, I'd expect that would hurt PIO throughput.
The main thing that makes me wonder "bug??" is the "ep3" handling, which is incomplete. That's the 8-byte Interrupt-IN endpoint that seems to be a "low priority" IRQ. If it does data toggle, then it should be called "ep3in-bulk", and you could test it by just using it as a substitute in for "ep2in-bulk" (except that it's got a very small maxpacket). If it can't toggle, call it "ep3in-int" and expect to write custom test code.
I've just implemented ep3 and have tried to test it using g_zero (substituting "ep3in-bulk" for "ep2in-bulk" as you suggest) but it has caused the host usbtest driver to crash when I plugged it in:
If it's that early, it suggests there's something wrong with the descriptors. They should look the same as before except that the endpoint number is 0x83 not 0x82, and the maxpacket for that endpoint (only!) would be 8 not 64.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
