-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add verbose (dump) option, report endpoint numbers, simplify device adaptions #1
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Tormod Volden <[email protected]>
Signed-off-by: Tormod Volden <[email protected]>
Signed-off-by: Tormod Volden <[email protected]>
"onexit" is used in the MinGW stdlib.h header file. Signed-off-by: Tormod Volden <[email protected]>
Nice one. No so sure if Wander will have time to update this repo after so long. In case you want to extend this, another thing is to sort out the issues under Windows. Minor changes will be required.
|
My mistake. I was not using the right branch. It is good.
|
The potential improvement is to take in more options, for example. |
Hmm, I already added -i for "IN only" and -o for "OUT only" in my tree but -i for interface is also logical. Alternatively we can use an "in" or "out" argument, instead of an option. |
No problem. We can even spell out more details like "intf" for interface and "altf" for interface alternate settings. |
-d VID:PID (hex) -i interface -a altsetting -e IN endpoint (hex, 0x80 will be or'ed) -u OUT endpoint (hex) An optional argument "in" or "out" limits the test to the given direction. Examples: iso-test -d 0483:5730 -i 1 -a 1 -e 2 -u 1 -n 44 -v iso-test -d 0483:5730 -i 1 -a 1 -u 1 out Signed-off-by: Tormod Volden <[email protected]>
Added options for VID/PID, interface, altsetting, endpoints: An optional argument "in" or "out" limits the test to the given direction. Examples:
|
I have been adapting this to my own test device, and these changes should be useful in any case.
What do you think about moving this to the libusb/examples tree? It could get some more attention there.