On 11/23/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
> On 11/23/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
> > On 11/22/07, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> > >
> > > On Thu, 2007-11-22 at 19:00 -0500, Jon Smirl wrote:
> > > > > It seems like AMCC does provide the necessary infos for
On 11/23/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
> On 11/22/07, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> >
> > On Thu, 2007-11-22 at 19:00 -0500, Jon Smirl wrote:
> > > > It seems like AMCC does provide the necessary infos for 4xx
> > > processors
> > > > though. Jon, do you think what
On 11/22/07, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2007-11-22 at 19:00 -0500, Jon Smirl wrote:
> > > It seems like AMCC does provide the necessary infos for 4xx
> > processors
> > > though. Jon, do you think what they provide is enough to use an open
> > > source debugger ?
On Thu, 2007-11-22 at 19:00 -0500, Jon Smirl wrote:
> > It seems like AMCC does provide the necessary infos for 4xx
> processors
> > though. Jon, do you think what they provide is enough to use an open
> > source debugger ?
>
> Do you have a link to the info?
Not at hand, but easy to find from A
On 11/22/07, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
>
> On Sun, 2007-11-18 at 01:47 +0100, Wolfgang Denk wrote:
> > In message <[EMAIL PROTECTED]> you wrote:
> > >
> > > > * The documentation is only available under NDA, a problem for open
> > > > source debuggers.
> > >
> > > This is wh
On Sun, 2007-11-18 at 01:47 +0100, Wolfgang Denk wrote:
> In message <[EMAIL PROTECTED]> you wrote:
> >
> > > * The documentation is only available under NDA, a problem for open
> > > source debuggers.
> >
> > This is what we need. I would like it specifically for the mpc5200.
> > But we want to
In message <[EMAIL PROTECTED]> you wrote:
>
> > * The documentation is only available under NDA, a problem for open
> > source debuggers.
>
> This is what we need. I would like it specifically for the mpc5200.
> But we want to use it in OpenOCD so NDA won't work.
It doesn't work. Been there a
On 11/14/07, Jerry Van Baren <[EMAIL PROTECTED]> wrote:
> Jon Smirl wrote:
> > On 11/13/07, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> >>> That's why Dominic wants to get OpenOCD running on the PowerPC. All we
> >>> need is the programming documentation for controlling the CPU via the
> >>
Jon Smirl wrote:
> On 11/13/07, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
>>> That's why Dominic wants to get OpenOCD running on the PowerPC. All we
>>> need is the programming documentation for controlling the CPU via the
>>> debug hardware.
>> Note that this is basically different for eve
gt; An: "Grant Likely" <[EMAIL PROTECTED]>
> > > CC: "Gerhard Pircher" <[EMAIL PROTECTED]>,
> linuxppc-dev@ozlabs.org
> > > Betreff: Re: Hardware debuggers for PPC74xx G4 CPUs
> > >
> > > Here are the choices:
> > > http
On 11/13/07, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
>
> > That's why Dominic wants to get OpenOCD running on the PowerPC. All we
> > need is the programming documentation for controlling the CPU via the
> > debug hardware.
>
> Note that this is basically different for every CPU around.
> That's why Dominic wants to get OpenOCD running on the PowerPC. All we
> need is the programming documentation for controlling the CPU via the
> debug hardware.
Note that this is basically different for every CPU around.
> Obviously this documentation exist, all of the commercial vendors had
>
ot;Gerhard Pircher" <[EMAIL PROTECTED]>, linuxppc-dev@ozlabs.org
> > Betreff: Re: Hardware debuggers for PPC74xx G4 CPUs
>
> > On 11/13/07, Grant Likely <[EMAIL PROTECTED]> wrote:
> > > On 11/13/07, Grant Likely <[EMAIL PROTECTED]> wrote:
> > &g
On 11/13/07, Olof Johansson <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 13, 2007 at 03:23:29PM -0800, Dan Malek wrote:
> >
> > On Nov 13, 2007, at 1:59 PM, Grant Likely wrote:
> >
> > >> Abatron BDI-2000.
> > >
> > > Oops, but that's not all that cheap. ($2750USD).
> >
> > If you place any value on y
On Tue, Nov 13, 2007 at 03:23:29PM -0800, Dan Malek wrote:
>
> On Nov 13, 2007, at 1:59 PM, Grant Likely wrote:
>
> >> Abatron BDI-2000.
> >
> > Oops, but that's not all that cheap. ($2750USD).
>
> If you place any value on your time or development
> schedule, it's a bargain.
That only applies
On Nov 13, 2007, at 1:59 PM, Grant Likely wrote:
>> Abatron BDI-2000.
>
> Oops, but that's not all that cheap. ($2750USD).
If you place any value on your time or development
schedule, it's a bargain. Just plug it in, and it works.
Choose any of your favorite debugger front ends,
from none with
Original-Nachricht
> Datum: Tue, 13 Nov 2007 17:10:29 -0500
> Von: "Jon Smirl" <[EMAIL PROTECTED]>
> An: "Grant Likely" <[EMAIL PROTECTED]>
> CC: "Gerhard Pircher" <[EMAIL PROTECTED]>, linuxppc-dev@ozlabs.org
> Bet
On 11/13/07, Grant Likely <[EMAIL PROTECTED]> wrote:
> On 11/13/07, Grant Likely <[EMAIL PROTECTED]> wrote:
> > On 11/13/07, Gerhard Pircher <[EMAIL PROTECTED]> wrote:
> > > I'm trying to debug a kernel lockup that occurs on my machine with all
> > > kernel
> > > versions >2.6.16. I don't have a c
On 11/13/07, Grant Likely <[EMAIL PROTECTED]> wrote:
> On 11/13/07, Gerhard Pircher <[EMAIL PROTECTED]> wrote:
> > I'm trying to debug a kernel lockup that occurs on my machine with all
> > kernel
> > versions >2.6.16. I don't have a clue what the root cause of this lockup is,
> > thus I'm thinkin
On 11/13/07, Grant Likely <[EMAIL PROTECTED]> wrote:
> On 11/13/07, Gerhard Pircher <[EMAIL PROTECTED]> wrote:
> > I'm trying to debug a kernel lockup that occurs on my machine with all
> > kernel
> > versions >2.6.16. I don't have a clue what the root cause of this lockup is,
> > thus I'm thinkin
On 11/13/07, Gerhard Pircher <[EMAIL PROTECTED]> wrote:
> I'm trying to debug a kernel lockup that occurs on my machine with all kernel
> versions >2.6.16. I don't have a clue what the root cause of this lockup is,
> thus I'm thinking about using a hardware debugger. Can anybody recommend a
> reaso
I'm trying to debug a kernel lockup that occurs on my machine with all kernel
versions >2.6.16. I don't have a clue what the root cause of this lockup is,
thus I'm thinking about using a hardware debugger. Can anybody recommend a
reasonably cheap hardware debugger that works with G4 CPUs and can in
22 matches
Mail list logo