On Tue, Jan 29, 2013 at 7:53 AM, Andreas Fritiofson <[email protected]> wrote: > 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.
Okay. > 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 ). Okay I agree with you here with regard to libftdi-1.0. Its async API does not use the full potential of libusb-1.0's async API anyway. But libusb-1.0's async API is not that to use, that is another story... > 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. If there are people like Laurent who wants to improve the D2xx code inside ft2232.c, I do not see why not let them do it. For people who want to use the other tools (which often use FTDI's driver and D2xx API) and OpenOCD at the same time, there is an advantage to stick to the ft2232.c and use the vendor FTDI driver. As for filter driver support of libusbx (libusb-1.0 fork), since I am both the admin of libusbx and libusb-win32, I can tell you that the filter driver is a low pripority for both libusb-win32 (if it works with some device, good, if it does not work for some other device, sorry) and libusbx (it should be able to make the filter driver works for USB composite device like FT2232x, since the filter driver works for FT2232x, but again this is a low priority). The ticket for the filter support of USB composite device is documented here. I will probably spend more time to diagnose the problem now that it is raised in both libftdi project and OpenOCD project. https://github.com/libusbx/libusbx/issues/72 -- Xiaofan ------------------------------------------------------------------------------ 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
