Good morning,
who is mainaining lsusb these days?
I recently sent a patch to Thomas Sailer <[EMAIL PROTECTED]>, which he reports is now merged into CVS. Fixes problems like:
- no parsing for common CDC class descriptors, - way-too-short control timeouts, - unforgiving (and sometimes wrong) string reads, - missing endpoint descriptor fields (one added in usb 2.0).
So it's more robust, and syslog doesn't accumulate anywhere near as many messages. (I didn't intentionally connect a set of devices, all of which gave "lsusb" indigestion, to test with -- but that's what I ended up with!)
There are several bugreports like this:
usbdevfs: process 17978 (lsusb) did not claim interface 0 before use
What does it mean? Is the application broken? If so, how can it be fixed?
It's a warning that could be fixed, nothing especially broken, but someone would have to patch it.
- Dave
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
