On Wed, Jun 24, 2009 at 23:30, Duane Ellis<open...@duaneellis.com> wrote: > Zach Welch wrote: >> Hi all, >> >> 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 compatible with libftdi, wraps ftd2xx >> 5) sockets: separate ftd2xx into their own process space >> 6) libusb+libftdi: The Right Thing To Do ;) >> > You are missing (7) - "WinUSB" - the windows platform type solution that > is simular to libusb. > Sadly, it does not go back to Win2K - but - most (popular) others are > solved.
Does WinUSB require any special privileges or signatures for a client that connects to the API? From my understanding libusb requires a kernel mode driver that needs to be installed by an admin first. If that is the case and if WinUSB can be used by the program without signing or admin privileges then WinUSB would seem the more practical approach. Michael _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
