What's more concerning is that after running the iso-out test my kernel log spews out
bad: scheduling while atomic! [<c027d3fc>] schedule+0x47c/0x490 [<c0106aec>] common_interrupt+0x18/0x20 [<c01040c3>] cpu_idle+0x33/0x40 [<c033079a>] start_kernel+0x19a/0x1e0 [<c0330380>] unknown_bootoption+0x0/0x160
Upgrading the usbtest driver to the 2.6.10 version seems to have solved this. Both the iso-out and the iso-in tests run fine now.
As for test 14 (control write), test.sh says "this relies on some vendor-specific commands". How do I know if my device and/or firmware is supposed to be able to handle those?
./testusb -a -t 14 -c 15000 -s 256 -v 1
gives
unknown speed /proc/bus/usb/003/005 /proc/bus/usb/003/005 test 14 --> 110 (error 110)
and
usbtest 3-1:1.0: TEST 14: 15000 ep0out, 0..256 vary 1 usb 3-1: control timeout on ep0out
in the kernel log. My USB Chief shows that the device consistently NAKs after 2 control OUT transfers (of 64 bytes each) of the patterned data. (Changing the size to 64 gives me lots of "usbtest 3-1:1.0: ctrl_out, byte 0 is 2 not 3" in the kernel log.)
-- Orjan Friberg Axis Communications
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
