On Wednesday 20 February 2008, Francis Moreau wrote: > Hello, > > I'm struggling with this module to test my udc. > > I loaded the zero driver like the following: > > $ modprobe g_zero pattern=1 > > and loaded usbtest module on the host: > > $ modprobe usbtest pattern=1 > > So I basically use the default parameters for both modules.
No; default params would not pass "pattern=1" on the command line. > Specially the 'buflen' parameter for the zero driver is 4096 bytes. > > To start the tests, I use the testusb user tool with the wrapper script > test.sh. > In this script, the buflen for the host is set to 2048. Which as you note is incompatible with "pattern=1". If you want to use "pattern=1" you need a different test script. > > I do: > > $ DEVICE=... test.sh in > > And it fails for test 2. The reason is because the buflen on the host > and the device > are different (2048 for the host and 4096 for the device). So once the host > get > the 2048 bytes from the device, it restart the same test and expect > the pattern to > restart to 0, However the device had queued a request of 4096 bytes, so the > new > loop still uses the old request which doesn't start to 0. > > Could anybody tell me what I'm doing wrong ? > > Thanks > -- > Francis > - > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
