Hi, I'm developing a peripheral controller driver for the Maxim Max3420e device using USB Gadget API for Linux. Max3420e device is USB 2.0 compatible but supports only full speed. I'm developing the driver under Linux Kernel 2.6.34-10. When testing this driver using -t8 of the testusb I get a --> 75 (Value too large for defined data type) error message. Client: modprobe g_zero autoresume=5 Host: ./testusb -a -c 1 -v 1 -t 8 unknown speed /proc/bus/usb/002/009 param->iterations 1 /proc/bus/usb/002/009 test 8 --> 75 (Value too large for defined data type) The default packet size in testusb is 512 bytes. Running the test consecutive times gives the same result. However, when I capture the USB traces (attached) I notice the following. For the first -t8 execution, the client returns 576 bytes (64b more than the defined packet size). Every subsequently -t8 execution returns 640 bytes (128b more than the defined packet size). In my simplistic conclusion, it seems that the host (i.e., testusb -t8) requests more bytes than what it can sustain but later complains of the packet size being too big. Could you please shed some light as to what may be causing this? Thanks! Edwin -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
