On Mon, Jan 28, 2013 at 3:16 PM, Xiaofan Chen <[email protected]> wrote:
> On Mon, Jan 28, 2013 at 9:25 PM, Laurent Gauch
> <[email protected]> wrote:
> > The mpsse.c should be called mpsse-libusb.c as it is actually.
>
> I tend to agree with you here. Technically you should be able to
> use libftdi-1.0 or ftd2xx to replace libusb-1.0 to achieve similar
> mpsse-libftdi1 and mpsse-ftd2xx.
Technically, of course. But would it make any sense? I see libmpsse (as it
would have been called if distributed separately, although there's another
lib with that name already which doesn't deserve it) as a direct
replacement of both libftdi and d2xx in a MPSSE application, that does the
job that those other libraries simply ignores.
I don't think it makes sense to replace libusb with libftdi since libftdi
is little more than a thin wrapper around libusb. And following your naming
suggestion, you should rename libftdi-1.0 to libftdi1-libusb1 (making my
library libmpsse-libftdi1-libusb1... :P ).
D2XX could work as a backend for people that absolutely must use the FTDI
driver. I'd rather wait for the filter driver to work.
/Andreas
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
