[subject changed and CC's trimmed]
On Tue, 2 Mar 2004, David Brownell wrote:
Yes, especially if it goes with a KERN_DEBUG message saying there are no ISO-IN splits yet. It's essentially all coded, but microframe scheduling needs tweaks for the IN cases. I decided to force ENOMEM until that code is ready ... someone willing to play with the code could turn it on and shouldn't find it needs many changes.
FWIW, I've simply disabled the check at the top of sitd_submit. Result: we are passing test 16 as well!
Seems like you had lots of success to report ... yowsza! Put a smile on my face ... :)
Of course, this just means someone brave needs to start testing webcams through TTs. I suspect there will be a few issues still lurking. Lots more than I want to fix, that's for sure.
/proc/bus/usb/001/004 test 14, 4.012137 secs
That's handy: control out testing makes "usbtest" cover a lot more of the basic host and device functionality.
Yep. In fact until very recently it was only working with -v0 for me. Reason was the handling of wLength=0 ep0 data packets. From the spec (5.5.3) it isn't clear to me whether the host whould send a zero-len packet in this case. My firmware assumed yes, but linux-usb didn't. I've changed the firmware now so they behave.
Seems like that TT issue I saw, maybe ... did OHCI and UHCI act the same?
- Dave
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
