Great, thanks.
On Mon, Sep 27, 2010 at 9:38 AM, Zach Welch wrote:
> On 09/27/2010 07:12 AM, John Rigby wrote:
>> On Mon, Sep 27, 2010 at 1:05 AM, Zach Welch wrote:
> ...
>>> Last week, I started testing my BeagleBoard with OpenOCD, so I have
>>> begun trying to validate and improve the Cortex-A8
On 09/27/2010 07:12 AM, John Rigby wrote:
> On Mon, Sep 27, 2010 at 1:05 AM, Zach Welch wrote:
...
>> Last week, I started testing my BeagleBoard with OpenOCD, so I have
>> begun trying to validate and improve the Cortex-A8 support. Indeed, I
>> have already committed a minor patch that fixed a bu
On Mon, Sep 27, 2010 at 1:05 AM, Zach Welch wrote:
> To All Ye Linaro Toolchain Folk, (and OpenOCD developers too)
>
> After a week of reading specifications and code, I am ready to start
> doing some serious hacking on OpenOCD. The following outlines my present
> plans and expectations, with the
On 27 September 2010 10:08, Loïc Minier wrote:
> Good notes on the valgrind release process; close to what I used to do
> at least
Yes, I should be thanking you as well, there's a reason you find them
familiar :-)
-- PMM
___
linaro-toolchain mailing
On Fri, Sep 24, 2010, Peter Maydell wrote:
> I have in turn used this as a pattern for writing up my notes/Loic's
> instructions
> on how to package a valgrind snapshot, so thanks!
> https://wiki.linaro.org/WorkingGroups/ToolChain/ValgrindReleaseProcess
> (it still has a few TODO entries in it, tho
Peter Maydell wrote:
>
> So we want to put our first snapshot out as soon as
> possible, labelled as a 'developer preview' or 'beta', to encourage
> people to start using it on ARM platforms and to report bugs.
> We can then work with upstream to hopefully get these bugs
> fixed by the time the va
To All Ye Linaro Toolchain Folk, (and OpenOCD developers too)
After a week of reading specifications and code, I am ready to start
doing some serious hacking on OpenOCD. The following outlines my present
plans and expectations, with the caveat that time can change everything.
Last week, I started
