On Sat, Apr 21, 2007 at 10:02:43AM -0700, David Brownell wrote: > On Saturday 21 April 2007, Hamish Moffatt wrote: > > > Test 14 passes when given suitable parameters (eg size 256, vary 1 by > > test.sh); > > the defaults fail with EINVAL. Now running test.sh for a thorough test. > > And when that runs over the whole weekend, you've hit the first > major milestone ... take a break! :) > > Presumably you've seen > > http://www.linux-usb.org/usbtest/ > > which talks about lots of other things to test. Make sure you test > the mass storage and network class drivers, since they both have some > quirks you can't uncove with gadget zero ... and run USBCV.
The default test.sh tests (control, in, out) ran 36 hours cleanly so far. USBCV passes also. Now trying some other things. Here's some other issues I've run in to; 1. Can't mount gadgetfs; mount says unknown filesystem, though it's listed in /proc/filesystems. My target device's kernel is a bit old, but this happens on my host even with 2.6.20.7(!). [ 4:02PM] [EMAIL PROTECTED]:~/tmp $ sudo modprobe gadgetfs [ 4:02PM] [EMAIL PROTECTED]:~/tmp $ sudo mkdir /tmp/gadget [ 4:02PM] [EMAIL PROTECTED]:~/tmp $ sudo mount -t gadgetfs none /tmp/gadget mount: unknown filesystem type 'gadgetfs' 2. When I run the 'unlink' tests (#11/12), I often get into a state where those tests pass, then everything else fails with error -110 until I rebind (unload/reload g_zero, or unplug/replug the cable). [ 4:19PM] [EMAIL PROTECTED]:~/tmp/testusb $ sudo ./test.sh unlink testing ALL recognized usbtest devices TESTING: unlink Mon Apr 23 16:19:25 EST 2007 test 11: 2000 read unlinks /proc/bus/usb/003/009 test 11, 33.345495 secs test 12: 2000 write unlinks /proc/bus/usb/003/009 test 12, 33.643430 secs Mon Apr 23 16:20:32 EST 2007 test 11: 2000 read unlinks /proc/bus/usb/003/009 test 11 --> 110 (error 110) 3. g_serial works, but zmodem transfers are flakey. I'm using use_acm=1. Device->Host transfers work at reasonable speed (sz on device reports over 100kbps), but receiving end reports a lot of retries. Host->Device zmodem transfers just timeout/error after the first block. Ymodem transfers complete ok. I see there was a big revamp of tty buffer handling a while back, which may have fixed this? As I mentioned above my kernel is a bit old. thanks Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
