Re: Report ID problem with HID-RAW interface usage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 30 Jun 2010 21:04:59 +0800
Xiaofan Chen <xiaofanc@xxxxxxxxx> wrote:

> On Wed, Jun 30, 2010 at 8:54 PM, Alan Ott <alan@xxxxxxxxxxx> 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?
> Then there is also libhid which is on top of libusb.
>

One of the advantages in the usb case is that you do not have to
_detach_ the kernel driver bound to the device in order to set/get
raw hid reports. With libusb this is needed.

> -- 
> Xiaofan
> 

Regards,
   Antonio

-- 
Antonio Ospite
http://ao2.it

PGP public key ID: 0x4553B001

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Attachment: pgp1V0NiZZTD4.pgp
Description: PGP signature


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux