Ingvar Stepanyan

Also, if I comment out `bMaxPacketSize0` check, the next to fail is `bcdDevice`: ``` Starting 8 threads Thread 2: device 0: mismatch in field bcdDevice: 256 != 20 Thread 7:...

> What is the device caussing the failure under Windows? ~~Hm it seems to be some generic HID USB device 1bcf:0005. It shows as disconnected in USBDeview, maybe that's why.~~...

Nvm, I looked at the wrong device that shared same vid:pid. It's actually my mouse: 

> git master: no issue That's because there was a bug in test where it would quietly continue after a error, see the change in stress_mt.c.

> EDIT 2: Ah, _hid_get_device_descriptor() hardcodes bcdUSB, bcdDevice, and bMaxPacketSize0 ... Ah that would do it. Would it be fair to call this a bug then? (since it doesn't return...

> It seems some devices/drivers will report LIBUSB_ERROR_NOT_SUPPORTED on open. If we ignore them the same way as LIBUSB_ERROR_ACCESS Is this different error code originating from drivers or from Windows...

> I don't know enough about HID to tell if it is possibly to get these values correctly. Worst-case, it should be possible to get them via control transfer like...

> LIBUSB_ERROR_NOT_FOUND Hm seems like a different problem, the one above was LIBUSB_ERROR_NOT_SUPPORTED.

> At least part of the reason for this is that some of the Linux host > controller drivers can't handle control transfers larger than that. > If you need...

> We should probably close this. 4k is plenty for control transfers. To me, I don't think it's about "how much you need" but rather about erroring too early and...