On Tue, 14 Mar 2006, Marc Singer wrote:

> On Tue, Mar 14, 2006 at 11:07:02AM -0800, Marc Singer wrote:
> > Test 14 is returnng an error 22, EINVAL.  It looks like this is due to
> > the parameters used in that test:
> > 
> >   usbtest 2-2:3.0: TEST 14:  1000 ep0out, 1..512 vary 512
> > 
> > The call is being made with the parameters
> > 
> >    (dev, param->iterations, param->length, param->vary)
> > 
> > and in the code, it checks for vary == length, which it is.
> > 
> >   if (length < 1 || length > 0xffff || vary >= length)
> >     return -EINVAL;
> > 
> > So, is this test supposed to be working?  I'm invoking it directly
> > 
> >   # testusb -a -t 14

It looks like you're using bad parameters.  For that test, it makes no
sense for vary to be >= length.  Try various random values for vary (but 
each less than 512, of course).

> Using the test.sh script, I get a different result.  According to USBMON, 
> the test transmits the following:
> 
>   e0865c40 984311403 S Co:057:00 s 01 0b 0000 0000 0000 0
>   e0865c40 984318037 C Co:057:00 0 0
>   e0865c40 984320233 S Co:057:00 s 40 5b 0000 0000 0100 256 = 00010203 
> 04050607 08090a0b 0c0d0e0f 10111213 14151617 18191a1b 1c1d1ee0865c40 
> 984321033 C Co:057:00 -32 8 >
>   e0865c40 984328828 S Co:057:00 s 01 0b 0000 0000 0000 0
>   e0865c40 984336037 C Co:057:00 0 0
>   e0865c40 984338146 S Co:057:00 s 40 5b 0000 0000 0100 256 = 00010203 
> 04050607 08090a0b 0c0d0e0f 10111213 14151617 18191a1b 1c1d1ee0865c40 
> 984339034 C Co:057:00 -32 8 >
> 
> What's odd is that there is no reponse from the UDC.  The dmesg output
> on the host shows this:

No, what's odd is that the log shows the same URB being submitted twice
with no completion in between (lines 3 and 4 above).  (Maybe that's what
you meant by "no response from the UDC".)  A line must have gotten dropped
from the log; usbcore should be smart enough to reject an URB submission 
while the URB is still in progress.

>   usbtest 2-2:3.0: TEST 14:  15000 ep0out, 1..256 vary 1
>   usbtest 2-2:3.0: ctrl_out, wlen -32 (expected 256)
> 
> So is this a problem with the test code?

Your usbmon log above doesn't show any -32 status values.  This tends to
confirm that some lines are missing.

Alan Stern



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to