search for: hid_report_type_featur

Displaying 4 results from an estimated 4 matches for "hid_report_type_featur".

2005 Oct 18
2
usb doesn't build on mac os x (10.4)
...ereferencing pointer to incomplete type hidups.c:180: error: dereferencing pointer to incomplete type hidups.c:180: error: dereferencing pointer to incomplete type hidups.c: In function 'getvalue': hidups.c:204: error: storage size of 'uref' isn't known hidups.c:209: error: 'HID_REPORT_TYPE_FEATURE' undeclared (first use in this function) hidups.c:210: error: 'HID_REPORT_ID_UNKNOWN' undeclared (first use in this function) hidups.c:216: error: 'HIDIOCGUSAGE' undeclared (first use in this function) hidups.c:204: warning: unused variable 'uref' hidups.c:220: wa...
2007 Jan 31
3
Re: [Nut-upsuser] Ablerex 625L USB version
...eportSize, 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_test, ReportSize); return rc; } else...
2018 Feb 16
0
[PATCH 1/3] Skip non-feature HID reports
...eport 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() iterates over all reports that were gathered from in the USB report descriptor...
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