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, Amit Nagal wrote:

> 1)
> 
> ioctl with which application can get  input / output feature report and size .

I am not sure I understand what exactly you mean.

hidraw intentionally doesn't interpret the reports, it's completely up to 
userspace application to do that.

> 2)
> 
> ioctl  which sets a flag so that when device sends a report , report
> id & report type  is prefixed
> to output of read() .
> i mean when application calls read , it gets input report as <report
> id ><report type ><payload >
> right now we get <payload > only .

Please see the commit 5a38f2c7c4dd53d5be097930902c108e362584a3. That makes 
sure that report id should be there properly. Do you still see any problem 
with this commit applied? (2.6.34 is the first kernel to have this one).

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


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

  Powered by Linux