Supporting a USB HID device interface that is missing a interrupt input endpoint
greg at kroah.com
Fri May 27 02:13:20 EDT 2022
On Thu, May 26, 2022 at 08:06:46PM +0000, Matt Silva wrote:
> Hey, Greg.
> I went ahead and started implementing the changes in libusb as per your recommendation. But I'm following up cause you asked about the usbhid-dump output.
> > But this really is not a HID device, right?
> Well, Windows does decide to recognize it as a HID device. I captured some packets send to the device's control endpoint of unknown transfer type with URB function: URB Function: URB_FUNCTION_GET_MS_FEATURE_DESCRIPTOR (0x002a). Perhaps that has something to do with this as my research says that MS OS Descriptors indicate which driver Windows should use.
Ah, yeah, this info, and the hid descriptor dump you provided means this
is ment to be controlled from userspace with a vendor-specific program
like you are writing using libusb.
So you are on the right path, nice work!
More information about the Kernelnewbies