Just pushed the fix for the errcode shadow warning along with various
improvements for fxload. I was hoping to get a chance to look into the
udev rules (see #29), but that's not going to happen before release.
Typos and other Changelog improvements will be applied with the official
1.0.15 relea
On 2013.04.14 13:01, Klaus Reimer wrote:
> I'm really confused about this libusb forking.
Then allow me to add add to your confusion:
Ever stopped to wonder why the libusb release candidates happen in an
private branch and not their mainline? Or wondered about what happened
to libusb releases 1.
On 04/14/2013 01:14 PM, Klaus Reimer wrote:
> I experienced a segfault in my program when I ported it to Mac OS X and
> hunted it down to the "libusb_get_active_config_descriptor" function in
> libusbx. I used version 1.0.14 but also tried 1.0.15rc3 and latest git
> HEAD with the same result.
Hm..
Hello,
I experienced a segfault in my program when I ported it to Mac OS X and
hunted it down to the "libusb_get_active_config_descriptor" function in
libusbx. I used version 1.0.14 but also tried 1.0.15rc3 and latest git
HEAD with the same result.
This is my test program (Which displays the
On Sat, Apr 13, 2013 at 2:43 PM, nico wrote:
>> You should use the 1.0.15rc3 since 1.0.14 has potential problem
>> with USB composite device.
>
> the user have tried with the 15rc3 with the same result (the device is a
> 0x0403, 0x6001)
You can see from my run log that I have a FTDI device with
V
