Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-27 Thread Zach Welch
On Mon, 2009-05-25 at 19:02 -0700, Zach Welch wrote: > On Sat, 2009-05-23 at 21:55 -0700, Zach Welch wrote: > [snip] > > 2) move board, target, and interface Jim script directories to src/tcl/ > > - this will move the whole directories intact, parallel to tcl/chip. > > - more structure can be

Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-25 Thread Zach Welch
On Sat, 2009-05-23 at 21:55 -0700, Zach Welch wrote: [snip] > 2) move board, target, and interface Jim script directories to src/tcl/ > - this will move the whole directories intact, parallel to tcl/chip. > - more structure can be added, if we see fit; this is a small step. > - > http://www

Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-24 Thread Zach Welch
On Sun, 2009-05-24 at 20:53 -0400, Duane Ellis wrote: > zach> [previous things] > david> > > Well, yes ... what eventually goes into /usr/include should > > be strongly limited to the interfaces. How anything gets > > implemented inside the library is nobody's busienss except > > for the library m

Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-24 Thread David Brownell
On Sunday 24 May 2009, Duane Ellis wrote: > > Really, we need to think *STRONGLY* about *NOT* creating "libopenocd" - > I believe creating "libopenocd" will be a nightmare (ie: the > implementation details in concrete) > > I believe that a public *SOCKET* interface with a *TEXT* based protocol

Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-24 Thread Zach Welch
On Sun, 2009-05-24 at 15:24 -0700, David Brownell wrote: > On Sunday 24 May 2009, Zach Welch wrote: > > >I'd suggest instead creating a > > > new include/ area to hold only files which will be getting > > > commitment for such public usage. > > > > This is common and I suppose that I s

Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-24 Thread Duane Ellis
zach> [previous things] david> Well, yes ... what eventually goes into /usr/include should be strongly limited to the interfaces. How anything gets implemented inside the library is nobody's busienss except for the library maintainers'. They should be able change how they do things easily. But

Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-24 Thread David Brownell
On Sunday 24 May 2009, Zach Welch wrote: > > I'd suggest instead creating a > > new include/ area to hold only files which will be getting > > commitment for such public usage. > > This is common and I suppose that I should have listed it (to be fair), > but I am not a particular fan

Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-24 Thread Zach Welch
On Sun, 2009-05-24 at 14:06 -0700, David Brownell wrote: > On Saturday 23 May 2009, Zach Welch wrote: > > 1) library header file rework: > > a) rename src/ as openocd/ (preferred) > > - this will allow public #include, e.g. > > b) do not rename src, e.g. #include > > - something needs

Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-24 Thread David Brownell
On Saturday 23 May 2009, Zach Welch wrote: > 5) commit testing tools >   - one-step smoke tests!  I probably need another week for this. >   - all in-tree with no new dependencies (maybe a Perl module or two) >   - > http://www.mail-archive.com/openocd-development@lists.berlios.de/msg04030.html W

Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-24 Thread David Brownell
On Saturday 23 May 2009, Zach Welch wrote: > 2) move board, target, and interface Jim script directories to src/tcl/ >   - this will move the whole directories intact, parallel to tcl/chip. >   - more structure can be added, if we see fit; this is a small step. >   - > http://www.mail-archive.com/

Re: [Openocd-development] 0.2.0 Pending RFCs

2009-05-24 Thread David Brownell
On Saturday 23 May 2009, Zach Welch wrote: > 1) library header file rework: >   a) rename src/ as openocd/  (preferred) >     - this will allow public #include, e.g. >   b) do not rename src, e.g. #include >   - something needs to be done; the library work is only half-complete >   - i have a pat

[Openocd-development] 0.2.0 Pending RFCs

2009-05-23 Thread Zach Welch
Hi all, The following RFC proposals are still on the table and need resolution: 1) library header file rework: a) rename src/ as openocd/ (preferred) - this will allow public #include, e.g. b) do not rename src, e.g. #include - something needs to be done; the library work is only hal