The hiddev interface appears to have a fundamental design flaw:
Report data is accessed via "usages", however multiple elements of
a report can have the same "usage" tag.
libhid came about because the design of HID power class devices depends on reusing the usage tags in different collections. libhid introduces the concept of a "path" to a report element, allowing you to distinguish (for instance) the measured voltage on the AC line from the battery voltage.
Again, your particular application probably does not need libhid in its entirety. Check the rewrite for some ideas on how to use libusb to directly perform HID transactions without the hiddev driver getting in the way.
-- Charles Lepple http://www.ghz.cc/charles/
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
