Displaying 4 results from an estimated 4 matches for "hid_desc_index".
2023 Nov 05
1
Passing hid_rep_index to libusb_get_config_descriptor is wrong?
@jimklimov: Looking at the code that uses hid_rep_index, hid_desc_index,
and hid_ep_in|out in usb_subdriver (all in nut_libusb.h)
I don't see any use of the addvars mechanism. If I follow the examples that
set and use those struct members, it looks like everything relies on them
being initialized to 0 by default, then only set in subdrivers or
situations that need...
2023 Nov 05
1
Passing hid_rep_index to libusb_get_config_descriptor is wrong?
...es, not the other way around.
>>
>> It looks like the most flexible thing would be to create a new member in
>> usb_communication_subdriver_t, maybe called usb_config_index (I don't know
>> if config descriptors are HID specific?) This member would be a lot
>> like hid_desc_index. It would default to zero but be available for those
>> USB subdrivers that needed something other than the default.
>>
>> Please let me know if I'm on the right track! In the meantime, I can get
>> my DIY project running for my specific device.
>>
>>
>>...
2023 Nov 05
1
Passing hid_rep_index to libusb_get_config_descriptor is wrong?
...pears to me that
configurations own interfaces, not the other way around.
It looks like the most flexible thing would be to create a new member in
usb_communication_subdriver_t, maybe called usb_config_index (I don't know
if config descriptors are HID specific?) This member would be a lot
like hid_desc_index. It would default to zero but be available for those
USB subdrivers that needed something other than the default.
Please let me know if I'm on the right track! In the meantime, I can get my
DIY project running for my specific device.
-------------- next part --------------
An HTML attachment w...
2023 Nov 05
1
Passing hid_rep_index to libusb_get_config_descriptor is wrong?
...rations own interfaces, not the other way around.
>
> It looks like the most flexible thing would be to create a new member in
> usb_communication_subdriver_t, maybe called usb_config_index (I don't know
> if config descriptors are HID specific?) This member would be a lot
> like hid_desc_index. It would default to zero but be available for those
> USB subdrivers that needed something other than the default.
>
> Please let me know if I'm on the right track! In the meantime, I can get
> my DIY project running for my specific device.
>
>
> __________________________...