On Wed, 30 Jun 2010, Xiaofan Chen wrote: > > Is that what you're asking for, or are you asking for something which will > > tell you which reports are _available_ on the device, and what their lengths > > are? There is currently no way to report which reports are _available_. As > > Jiri said, HIDRAW does not do any parsing of the report descriptor. All data > > is passed "raw" from the user application to the device. > > > > If you know what type of device you are talking to, then you shouldn't > > really need to parse the descriptor in software, because you'll know what > > the device supports, right? > > Sorry I do not know much about hidraw. However, if HIDraw is so > "raw", what are the benefits of HIDRAW compared to using libusb? It's independent on transport below HID protocol. I.e. it works for Bluetooth HID devices as well (and any potential HID devices over different transport protocol that might come in the future). > Then there is also libhid which is on top of libusb. Which is basically comparable to hiddev -- i.e. USB only, and performs report processing and parsing. -- Jiri Kosina SUSE Labs, Novell Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
