Just pushed the fxload sample fix as well as the libusbK bulk transfer workaround (switch ALLOW_PARTIAL_READS pipe policy to enabled by default). I also pushed Ludovic's xusb fixes for #42, with some modification. See the comment from https://github.com/libusbx/libusbx/pull/42.
Since I'd like Travis to have a look into it at some stage, as I'm pretty sure it's a K bug, I've been trying to figure out where to log a tracker issue for libusbK, but didn't manage to find out where to do that in SF's new tracker. Would it be possible to have one logged? Besides the USB 3.0/bMaxPower patch, which I'll try to push tomorrow, 2 other items I would still consider open for 1.0.13 would be: - The pkg-config --static and libusb-1.0.pc issue (for which I created issue #43: https://github.com/libusbx/libusbx/issues/43) - libusb_error_name() for transfer status codes At this stage, I'm not planning to do any work on those (no time), but I'll probably accept a patch if someone wants to submit one. Regards, /Pete ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
