2012/9/4 Xiaofan Chen :
> Here are two links from libusb mailing list, saying to include the
> extra libraries needed for static linking in Libs.private in the pc file.
> http://libusb.6.n5.nabble.com/libusb-1-0-pc-files-when-static-linking-td43.html
> http://libusb.6.n5.nabble.com/How-to-use-stati
> While I have to say your code is A LOT cleaner than the fxload one
That's because I'm not very smart - breaking problems down is the only
hope I have of solving them!
> (and at the very least, I'd like to use your firmware with the vendor
> commands for eeprom flashing),
If you want to adopt
On 2012.09.04 10:27, Chris McClelland wrote:
> If you want to adopt that firmware code, I'm fine with you changing the
> license to LGPLv2.1 to match your code, provided you keep the
> attribution.
As somewhat of a license and GPLv3 zealot, I'd be very uncomfortable
asking you to change your lice
Hi Anthony,
On 2012.09.04 04:15, Anthony Clay wrote:
> I've been unable to test isochronous
> transfers. Obviously, Winusb doesn't support them - but I thought that
> libusbK does - maybe it is not implemented w/libusb (yet?).
That's exactly the case. It's the usual case of too much to do with t
I have a prototype dual video display that will require it. It's a high
speed device that requires two compressed 512x512 (max) video streams.
It's not at the top of my todo list, but I'll *gladly* contribute and test
once it finally does. Mainly, I wanted to get my "Libusb++"
wrapper-library rea
Greetings all,
I've spent the last couple of weeks building a wrapper for libusb to save
time while developing native c++ applications. It completely hides the
libusb implementation inside of an object-oriented framework. It's based
around a USB "Device" class that can be instanced easily using
