32bit Usage items are not supported by get_usage of libusb backend #454

Closed
opened 2022-09-11 08:23:38 -05:00 by JoergAtGithub · 2 comments
JoergAtGithub commented 2022-09-11 08:23:38 -05:00 (Migrated from github.com)

The USB standard allows it to specify a usage in two ways:

  • Fully qualified as one single 4 byte report descriptor Usage item
  • Seperated in an 1 or 2 byte Usage-Page item, followed by an 1 or 2 byte Usage item
    The get_usage function of the libusb backend supports only the second.

From USB HID spec 1.11 page 17:
grafik

From USB HID spec 1.11 page 35:
grafik

The USB standard allows it to specify a usage in two ways: - Fully qualified as one single 4 byte report descriptor Usage item - Seperated in an 1 or 2 byte Usage-Page item, followed by an 1 or 2 byte Usage item The get_usage function of the libusb backend supports only the second. From USB HID spec 1.11 page 17: ![grafik](https://user-images.githubusercontent.com/64457745/189529023-f800f2e9-85b2-4bac-bfce-68b17604c11a.png) From USB HID spec 1.11 page 35: ![grafik](https://user-images.githubusercontent.com/64457745/189529415-61ed0bc9-b26b-4b7e-b16d-a3b63b018589.png)
mcuee commented 2023-05-10 04:32:00 -05:00 (Migrated from github.com)

Is it because most of the USB HID Devices use the second way that we have not seen bug report for thr libusb backend?

Is it because most of the USB HID Devices use the second way that we have not seen bug report for thr libusb backend?
Youw commented 2023-05-10 04:37:49 -05:00 (Migrated from github.com)

Yes, likely

Yes, likely
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-libusb/hidapi#454
No description provided.