mcuee
mcuee
Not so sure if this is relevant now.
libusb-win32 project is in a support only mode. Mailing list support is still provided, no changes to the codes and release.
libusb-win32 project is in a support only mode. Mailing list support is still provided, no changes to the codes and release.
libusb-win32 project is in a support only mode. Mailing list support is still provided, no changes to the codes and release.
For isochronous transfer, please use libusbk.sys or WinUSB. So I will keep wontfix label here.
Mailing list discussion in 2011. https://sourceforge.net/p/libusb-win32/mailman/libusb-win32-devel/thread/BANLkTimkAAVgX00nKDSBqc4FRQYt4onPAw%40mail.gmail.com/#msg27481705
Patches submitted: ``` Index: src/driver/transfer.c =================================================================== --- src/driver/transfer.c (revision 398) +++ src/driver/transfer.c (working copy) @@ -199,6 +199,13 @@ return IoCallDriver(dev->target_device, irp); } +void FixBuffer( struct _URB_ISOCH_TRANSFER *UrbIsochronousTransfer) +{ + unsigned...
> I am planning on using this driver for a long time, so if there is something broken in ISO support, the please report it. > > Is it all...
Some info here from libusbk website. http://libusbk.sourceforge.net/UsbK3/usbk_comparisons.html 1) libusbK.sys advantages when compared to libusb0.sys: Winusb-like power management. Winusb-like pipe policies. Driver-level asynchronous transfer timeouts. Improved isochronous transfer support. Newer, more...
One old proposal of improvement: - https://github.com/mcuee/libusb-win32/issues/2