On Fri, Apr 20, 2007 at 11:15:25AM -0400, Alan Stern wrote: > On Sat, 21 Apr 2007, Hamish Moffatt wrote: > > 1. Why would I be getting ETIMEDOUT instead of the expected EPIPE? It > > looks like this will affect a lot of tests in case 10 too. > > ETIMEDOUT means that the gadget didn't reply to the request. That is, it > kept sending NAKs instead of sending STALL. Your driver isn't halting > endpoint 0 when it should.
Spot on. Having fixed that, tests 9 and 10 now pass. In fact everything but 14 now passes, which I'll investigate next. > > I changed it to accept ETIMEDOUT. Now I get a timeout every time > > through this test, but it does pass. However, testusb's default is > > to run 1000 iterations, which will take a long time with a 5 second > > timeout each. > > You shouldn't subvert the test, you should fix your driver. Obviously. Indeed. I didn't mean to suggest any fault in usbtest, rather just needed assistance understanding why my tests were failing. > > 3. udev->speed is actually an unknown value (not _LOW, _FULL or _HIGH) > > for my device apparently. I haven't researched this yet; is there an > > obvious reason? > > What on earth are you talking about? It must be USB_SPEED_FULL. Have you > tried printing out the value to see? usbtest does this (in usbtest_probe()) and it's reporting unknown. Dave's post suggests I am neglecting to set this to full correctly in my gadget. Yet to look into this. 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
