On Nov 24, 2008, at 3:24 AM, Spen wrote:
Hi,
I have created a release 1.0 branch:
svn://svn.berlios.de/svnroot/repos/openocd/branches/openocd_1_0_branch
if no major issues are found after say 1 month then we will tag a
release.
I can test the st/pic32 targets, if anyone has any free time t
> All jtag taps are kept in a linked list, head:
>
>OLD:extern jtag_device_t *jtag_devices";
>NEW: extern jtag_tap_t *jtag_all_taps;
are you keeping two lists? One list for active and one for
all taps?
> 2) There is a ghost variable (that holds the length of the list)
>OL
Rick Altherr wrote:
>
> On Nov 23, 2008, at 10:10 AM, Carlos Antunes wrote:
>
>> Rick Altherr wrote:
>>>
Debug: 298 216881 target.c:1787 target_wait_state(): waiting for
target debug-running...
>>>
>>> This _appears_ to be coming from arm7_9_dcc_completion(). That
>>> method is speci
On Nov 24, 2008, at 5:17 PM, Duane Ellis wrote:
All,
I've been working some on support for the beagleboard (oma3530) -
you've
seen quite a bit of traffic on the mailing list about this.
I need to break these changes in two parts.
One thing that is shaking out of this is the removal of the
All,
I've been working some on support for the beagleboard (oma3530) - you've
seen quite a bit of traffic on the mailing list about this.
I need to break these changes in two parts.
One thing that is shaking out of this is the removal of the "tap index"
idea, and going with a uniform "tap name
Rick Altherr wrote:
On Nov 23, 2008, at 10:10 AM, Carlos Antunes wrote:
Rick Altherr wrote:
Debug: 298 216881 target.c:1787 target_wait_state(): waiting for
target debug-running...
This _appears_ to be coming from arm7_9_dcc_completion(). That
method is specified to be called at the e
Spen wrote:
> I have created a release 1.0 branch:
> svn://svn.berlios.de/svnroot/repos/openocd/branches/openocd_1_0_branch
> if no major issues are found after say 1 month then we will tag a release.
>
> I can test the st/pic32 targets, if anyone has any free time to check other
> targets that wou
Hi,
I have created a release 1.0 branch:
svn://svn.berlios.de/svnroot/repos/openocd/branches/openocd_1_0_branch
if no major issues are found after say 1 month then we will tag a release.
I can test the st/pic32 targets, if anyone has any free time to check other
targets that would be good.
Like i
> > Any objections/comments?
>
> Instead of trying to *guess* when is a good time to cut a
> branch, lets just pick a version everybody is happy with and
> work from that.
>
we are not guessing, we are creating a release branch that will be as such
frozen except for major bug fixes.
if after t
On Mon, Nov 24, 2008 at 11:51 AM, Spen <[EMAIL PROTECTED]> wrote:
>> > Any objections/comments?
>>
>> Instead of trying to *guess* when is a good time to cut a
>> branch, lets just pick a version everybody is happy with and
>> work from that.
>>
>
> we are not guessing, we are creating a release br
10 matches
Mail list logo
