On Sun, Dec 9, 2012 at 7:07 PM, Chunning Ha <[email protected]> wrote: > 2. Adding a group of new data structures and rewrite the corresponding > functions; > In this way, we have got to rewrite too much code. And existing code > will not be affected. But we have to another set of code, which got > very few differences with existing code. > > 3. Change the "framework" so that 32, 64 bit will be supported. > Very hard work. Almost all existing code will be affected seriously.
These two are good. After I finish the work on SWD (its done, today I have sent them for a review, but need to wait until next week for fixes reported jenkins) I will reorganize internals of the OpenOCD and rewrite most of the code, so your job on 64-bit support (and others) has good option to be implemented in a correct but more difficult way from the beginning :-) Are you already familiar with the internals of the OpenOCD? It will take some time until you do :-) I am not yet familiar with the MIPS in OpenOCD (I was working on ARM so far) but have already couple of devices and willing to know them better from inside, so count me as companion for the work :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
