Re: [Openocd-development] policy vs. mechanism

2009-12-02 Thread David Brownell
On Tuesday 01 December 2009, Zach Welch wrote: > > However ... splitting ft2232.c into chunks would be good. > > One per adapter.  It's quite a mess now. > > I just mentioned this to someone else today off-list!  It's like you're > reading my mind  eeek! ;)  Creepy!  Great minds think alike.

Re: [Openocd-development] policy vs. mechanism

2009-12-01 Thread Zach Welch
On Tue, 2009-12-01 at 20:57 -0800, David Brownell wrote: > On Tuesday 01 December 2009, Zach Welch wrote: > > After the command cleanup that I have started, I believe this type of > > factoring deserves to be pursued in the other modules. I propose making > > these changes in the following order:

Re: [Openocd-development] policy vs. mechanism

2009-12-01 Thread David Brownell
On Tuesday 01 December 2009, Zach Welch wrote: > After the command cleanup that I have started, I believe this type of > factoring deserves to be pursued in the other modules.  I propose making > these changes in the following order: > >  - svf, xsvf, pld: simple core/tcl separation: */core.c and

[Openocd-development] policy vs. mechanism

2009-12-01 Thread Zach Welch
Hi all, Part of my impetus to restructure the command set is to see more separation of policy and mechanism in the code. The JTAG layer shows how this can be done: a tcl.c file contains all of the command handlers, while core.c contains the low-level functions that do the work. It might be worth