On Wednesday 09 February 2005 11:03 pm, Jamie Guinan wrote: > Here is a summary of a few tests... > > [ Test 1: gadget_zero <-> testusb ] > target# modprobe usbtest > target# modprobe g_zero > target# modprobe lh7a40x_udc > > host# modprobe usbtest > host# ./testusb -a > unknown speed /proc/bus/usb/001/004 > /proc/bus/usb/001/004 test 0, 0.000001 secs > /proc/bus/usb/001/004 test 1, 0.999836 secs > /proc/bus/usb/001/004 test 2, 0.999843 secs > /proc/bus/usb/001/004 test 3, 0.999837 secs > /proc/bus/usb/001/004 test 4, 0.999843 secs > /proc/bus/usb/001/004 test 5, 17.943017 secs > /proc/bus/usb/001/004 test 6, 16.997171 secs > /proc/bus/usb/001/004 test 7, 17.946013 secs > /proc/bus/usb/001/004 test 8, 16.997172 secs > /proc/bus/usb/001/004 test 9, 10.998167 secs > /proc/bus/usb/001/004 test 10, 15.998353 secs > /proc/bus/usb/001/004 test 11, 3.998333 secs > /proc/bus/usb/001/004 test 12, 3.999331 secs > /proc/bus/usb/001/004 test 13 --> 22 (error 22) > /proc/bus/usb/001/004 test 14 --> 22 (error 22)
Which is basically positive. Test 13 is for halt processing, while test 14 is for control-OUT transfers. I suspect neither of those just happens to be implemented yet (assuming the hardware supports both of them). The control-OUT stuff would be good to get working, so that RNDIS can be used; the halt processing would probably help make fault paths in g_file_storage work better. > [ Test 2: serial gadget <-> generic USB serial ] > target# modprobe lh7a40x_udc > target# modprobe g_serial > > host# modprobe usbserial vendor=0x0525 product=0xa4a6 I'd have thought by now that usbserial would have been taught to understand that driver! An alternative would be using g_serial in the cdc-acm mode. > target# cat > /dev/ttygs0 > Hello, how are you doing. > Fine, thanks. > > > host# cat < /dev/tty/USB0 > > Hello, how are you doing. > > Ho,w ydo. > > Hddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > dddddddddddddddddddddddddddddddddddddddddddddddddddddd\ > ddddddddddddddddddddddddddddddddddddFine, > thanks. > > dF, nk > > [ End test 2 ] Hmm, well that's less successful. It reminds me of a problem someone else reported not long ago. You didn't say what kernel you're running on the lh7a404 ... it'd be worth making sure at least the serial gadget driver there matches the latest kernel.org kernel. - Dave ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
