Le 17.01.2013 21:24, CeDeROM a écrit : > On Thu, Jan 17, 2013 at 9:12 PM, Laurent Gauch > <[email protected]> wrote: >>> How can it seem like a good idea to add *another* set of files? >>> That's just insane. I think the sane approach is to simply delete >>> ft2232.c and move on. It sounds like Tomek already has ideas about >>> how to use mpsse.c which is great! >>> >> End why deleting something working ? Stupid idea ! The ft2232.c has the >> advantage to specify the layouts. The mpsse is a good code source, but >> the new ftdi.c should integrate the layout specific things instead to >> have to specify from tcl ... So the ft2232.c has still serious >> advantages over ftdi mpsse. > Hello Laurent :-) I agree that we should not remove something that is > working and has its users, at least for backward compatibility > reasons. However, moving out initialization from the source code to > TCL has some advantages - we could select transport first and have one > configuration file for an interface that will choose proper > initialization routine based on selected transport, which seems to be > impossible at the moment with current ft2232 design where all > initialization routines are hardcoded into the source code... > Yes you are right for the TCL advantage, but this is for the developper point of view. For 95% of the end users, it is much more better to have it 'hardcoded' avoiding to open a dongle with a wrong layout !
But your added TCL GPIO is a good features - Thank you for that. >> And the ft2232.c allows to use d2xx driver. Which one was why the >> openocd comes popular, since the d2xx was faster and much more stable >> than the libusb. > I guess new mpsse driver with new libusb-1 can be even faster and > still it is full open-source, but I did not try that one yet :-) > Yes, the mpsse driver is a great start point, but it is still not ideal. It should be called mpsse_libusb.c. The actual mpsse.c is too much oriented libusb. The mpsse is just a tx rx request response protocole. It should not implement the libusb specific things. The same mpsse protocol could be used over ethernet or over other TX RX wireless communication. ftdi.c + mpsse.c should be mpsse_hla.c mpsse.c mpsse_libusb.c to be ideal and really layer oriented. > Best regards :-) > Tomek > Regards, Laurent Gauch http://www.amontec.com ------------------------------------------------------------------------------ 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/learnmore_122712 _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
