Control endpoint doesn't support multiple packets about gousb HOT 2 CLOSED

I don't think that is correct - wLength is used, it's set to the length of the data slice that is passed to the call. See

The underlying C method, libusb_control_transfer, needs the wLength argument simply because in C the request data is passed as a pointer, with no inherent length; the library needs to be explicitly informed of the size of the transfer buffer.

If I remember correctly, all of the methods implemented in this library rely on the host handling the packet splitting. So just like our InEndpoint.Read/OutEndpoint.Write accept arbitrary data buffer lengths and expect libusb to split the whole transfer into packets, I'd expect Control to do the same.

Can you explain the use case and show the code that you use? Ideally you could also attach the libpcap dump of the USB transfers that you see when you use data length > max packet length.

from gousb.

Thanks for your response -- closing this as I think I was looking at the wrong source & misunderstanding the root of my own issue

from gousb.