Displaying 3 results from an estimated 3 matches for "hid_report_get".
2007 Jan 31
3
Re: [Nut-upsuser] Ablerex 625L USB version
...Entering libusb_get_report, ReportSize: %i,
ReportSize_test: %i",ReportSize, ReportSize_test);
if (udev != NULL)
{
rc = usb_control_msg(udev,
USB_ENDPOINT_IN + USB_TYPE_CLASS +
USB_RECIP_INTERFACE,
0x01, /* HID_REPORT_GET */
ReportId+(0x03<<8), /* HID_REPORT_TYPE_FEATURE */
0, raw_buf_test, ReportSize_test, USB_TIMEOUT);
p_raw_buf_test = raw_buf_test +
(ReportSize_test - ReportSize);
memcpy(raw_buf, p_raw_buf_t...
2018 Feb 16
0
[PATCH 1/3] Skip non-feature HID reports
...that it would get an Input report ID confused with a Feature report ID
> (unless interrupt_only is set, as it is for powercom devices).
libusb_get_report() has:
ret = usb_control_msg(udev,
USB_ENDPOINT_IN + USB_TYPE_CLASS + USB_RECIP_INTERFACE,
0x01, /* HID_REPORT_GET */
ReportId+(0x03<<8), /* HID_REPORT_TYPE_FEATURE */
0, raw_buf, ReportSize, USB_TIMEOUT);
Hence, libusb_get_report() always requests the report ID as a feature
report, and never uses the report type that was stored.
This means that when HIDDumpTree() iterate...
2018 Feb 15
2
[PATCH 1/3] Skip non-feature HID reports
On Feb 3, 2018, at 7:19 PM, Russell King wrote:
>
> Input and Output reports are used for interrupt endpoints rather than
> control endpoints. HIDGetItemData() only ever requests feature
> report IDs, and requesting non-feature report IDs as feature IDs may
> lead to undesirable results and errors.
This one made me scratch my head a bit.
I don't think it's unreasonable