On Tue, Jan 22, 2013 at 4:10 PM, Spencer Oliver <[email protected]> wrote: >> If you know any better solution, please show it working, because your >> simple statements in words is really extremely hard to implement in >> code and would require changes both in code, configuration and >> internals organization anyway. We can wait for it and have no SWD >> working, or use what is already available. I prefer to put my time and >> work into mpsse driver than extending ft2232 driver that is considered >> obsolete. If you think master branch and other people should wait for >> mpsse driver working with swd/libswd and other people also want this, >> then we will wait until mpsse driver is ready to work with >> transport/swd, I will work on it :-) >> > > This is what i am looking into.
My point of view: Stuff can be tested with ft2232 and we should put efforts to make swd work with other drivers like mpsse and hla, no need to work further on ft2232. ft2232 is an initial interface that allows testing. Thats all, absolutely no sense in redesigning ft2232. I have put lots of time and effort to make things work and commits that will add this functionality maintaining backward compatibility. Instead messing with existing code I would prefer to fix the HLA issues and move forward. I have also introduced some changes where it was possible to present new organization of OpenOCD - it had to be done anyway, so when I was working on that part, simply I did what had to be done.. > I am also looking into all the current swd issues, i am as keen as you > to get this merged. > > I do understand all the things you have said above, however we are not > going to merge something that is not complete/working. I think your renaming of stuff and splitting and merging commits makes no sense at all, because you have better things to do. I have prepared those patched carefully, introducing changes step by step. After they are introduced, one or two commits after them code will look exactly the same. The difference is in time of your work - you want to put time on my patches which are clean in my opinion, or you can put time on your HLA drivers to make work with new design. Lets move forward :-) > If something else needs changing in OpenOCD, then fine lets change it > and make the swd changes a dependant. When I got into the task some time ago I had two choices - clean up the internals, or work on the swd implementation. I have chosen second - to create platform and solution independent swd framework. Its ready. Now I want to do the internals reorganization. If you want me to make internals reorganization first, then for long time there will be no swd implementation in OpenOCD and my time wil be wasted :-( Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ------------------------------------------------------------------------------ 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
