|
From: Nikolai K. <sp...@gm...> - 2010-07-20 15:27:49
|
On 07/20/2010 06:59 PM, Alan Stern wrote: > Maybe, although if you can narrow the trace down to the device or > interface in question then all the non-HID stuff would be eliminated. Yes. It seems I didn't give enough thought to this idea. Maybe it's because I arrived to the need for such tool from a different direction. I think I could use it if my attempts at the tool fail or it proves insufficient. > Exactly what you want to do isn't clear. Sorry, my fault. I want to simply dump whatever a device transmits via its HID interface interrupt IN endpoints when it is operated in different ways (all of them, preferably). My idea (possibly naive and insufficiently verified) is that a lot of input devices not working with Linux could be made to work by fixing their report descriptors. Not really fixing, but just feeding the generic HID driver with a fixed one. For that I need to get the report descriptors and reports themselves. I can't own or rent all such devices, so I plan to ask their owners to collect diagnostics for me, plus maybe get some shop assistants to give me 5 minutes with them to collect it myself. The diagnostics tool set is just a console "wizard" asking the user to do some input and recording whatever was produced when it was done. I have most of it implemented for graphic tablets, but it dumps evdev events instead currently. > Would you be satisfied simply to have an option in libusb for printing out > a record of all the data getting sent or received? Thank you :) Well, it would do if nothing else works, of course. But I think the tool would be better. Thanks for interrogating me, I understand I wasn't clear enough :) Sincerely, Nick |