I've been working on some kernel usbfs changes to make live easier for
libusbx, consisting of 2 API additions:
1) An API to query the kernel if it supports things like the
bulk-continuation flag and other features for which we currently abuse
the kernel version to find out if they are suppor
With the latest kernels it is no longer needed to always split large bulk
transfers into multiple urbs. This patch takes advantage of this by not
splitting when not necessary. Note that the non-split code path is in essence
using the old split code path with an urb count which is always 1.
This le
There were a few (new) usbdevfs capabilities which libusb could not
discover in any other way then checking the kernel version. There are 3
problems with this:
1) It is just not very pretty
2) Given the tendency of enterprise distros to backport stuff it is not
reliable
3) Some of these features
On 2012.06.29 10:14, Jach Fong wrote:
> The xusb.exe in released 1.0.12 also have the same result.
>
> I think the problem mostly was caused by my device. It is a device
> I had built years ago using Silabs' F8051F320 and their Development tool
> Version 2.2 with included HID example source.
Aha,
On 28 Jun 2012 Pete Batard Wrote:
> To eliminate the compiler, can you please download the
> libusbx-1.0.12-win.7z from
> http://sourceforge.net/projects/libusbx/files/releases/1.0.12/Windows/
> and run the xusb.exe you find there in examples/bin32, prerablly with
> LIBUSB_DEBUG=4. If you get
