> Just one more clarification. libusb-win32 can be made to support Vista
> 64bit and Windows 7 as well with a digital signature. It already works
> under XP 64bit.
>
> Vendors can also use libusb-win32 as their default device and get
> it WHQLed with their particular VID/PID if they want to do t
> Here is the full list of GPL-compliant solutions for libftd2xx GPL
> compliance, after further review, consideration, and enumeration:
>
> 1) Documentation: build it yourself!
> 2) Build-Kit: automate the build on users' machines
> 3) XXX: to be revealed, if legal
> 4) libftdi-ftd2xx: ABI comp
On Tue, 2009-06-23 at 20:23 +0100, Zach Welch wrote:
> On Tue, 2009-06-23 at 20:19 +0100, Ian Guffick wrote:
>> Hello to all,
>>
>> I don't want to get involved in the 'war' that seems to have erupted over
>> this issue.
>> I am a user of OpenOCD ra
Hello to all,
I don't want to get involved in the 'war' that seems to have erupted over
this issue.
I am a user of OpenOCD rather than a developer, I regularly grab SVN head
and compile it under Cygwin for Windows with FTD2XX.lib. And I will continue
to do so for my private build.
It is clear
Hello,
When using an FTDI FT2232 based JTAG interface, what limits the JTAG speed?
Is it the 12Mb/s USB or the maximum JTAG clock allowed for the attached CPU?
I've noticed that FTDI have a new device (FT2232H) that uses Hi-Speed USB
(480MB/s).
At first glance it seems to have the same features
