On Wed, 1 Mar 2006, Marc Singer wrote: > My question is simple. How can I inspect a dump from USBMON and > indentify something that is a wrong result? Assuming that the message > order produced by the UHCI driver is correct (it's too late to go > buying a hub right now), and I suspect that it is correct, I'm seeing > about 30 outstanding requests before the replies come back. Is this > wrong?
No, it's one of the things that particular test is meant to try out -- submitting a large queue of requests to see if the HCD can handle it properly. > In order to make sense of a test, I need to be able to determine what > when the output is wrong? Is the output of test.sh the only thing > that I can depend on to tell me when there is an error? Not at all. You can read the source code for the tests in drivers/usb/misc/usbtest.c. Then knowing what the test sends, you can know what the correct result should be. Alternatively, you can carefully read through the usbmon output and match replies against requests. Knowing the request, you ought to be able to tell if the reply is correct. Or you can compare the usbmon output with a known working test (one made using dummy-hcd). 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
