Peter Dons Tychsen

Yes, any contributions are welcome

> Running the static driver verifier can maybe be included? https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/static-driver-verifier This should probably be added to the build system

We can follow this: https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/using-static-driver-verifier-to-find-defects-in-drivers

The static driver verifier will be added to the build system after the first release of 3.0.0.X Also, all errors and warnings will be fixed that is emitted by this...

Hi @sonatique OK, I think i know what is going on. The problem here is that you rack up 10 transfers which are all directly submitted to the underlying driver...

@dontech : thanks for the explanation. No, I am not sure at all that I am missing data vs disordered. I didn't investigate more as I wanted to reproduce with...

Just verified it. This is exactly what is happening. libusb0-sys:[transfer_complete] sequence 7: 64 bytes transmitted, maximum_packet_size=64, totalLength=128 libusb0-sys:[transfer_complete] sequence 8: 64 bytes transmitted, maximum_packet_size=64, totalLength=64 libusb0-sys:[transfer_complete] sequence 7: 0 bytes...

The basic problem is that you expect the data to arrive in the same order as your read requests. Yes, indeed. There have been several discussion on libusb-1.0 github regarding...

Looks like I'll have to choose in between more than one transfer or transfer size >64K... Damned. Its not related to 64K directly. It is related to the endpoint size....

@dontech What I meant is that I have to choose to either stay with current official release and have more than one buffer but of no more than 64KByte in...