From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Wolfgang Denk <wd@denx•de>
Cc: Olof Johansson <olof@lixom•net>, linuxppc-dev@ozlabs•org
Subject: Re: Hardware debuggers for PPC74xx G4 CPUs
Date: Fri, 23 Nov 2007 10:37:05 +1100 [thread overview]
Message-ID: <1195774625.6970.145.camel@pasglop> (raw)
In-Reply-To: <20071118004729.67824247F1@gemini.denx.de>
On Sun, 2007-11-18 at 01:47 +0100, Wolfgang Denk wrote:
> In message <9e4733910711141834n2bfb1742v5637c56e27e26f5a@mail•gmail.com> 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 logn time ago. It's and endless
> fingerpointing. Freescale (by then: Motorola) says they cannot
> release any information because of their contracts with IBM, and vice
> versa.
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 ?
Ben.
next prev parent reply other threads:[~2007-11-22 23:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 21:48 Hardware debuggers for PPC74xx G4 CPUs Gerhard Pircher
2007-11-13 21:57 ` Grant Likely
2007-11-13 21:59 ` Grant Likely
2007-11-13 22:10 ` Jon Smirl
2007-11-13 22:21 ` Gerhard Pircher
2007-11-14 1:17 ` Benjamin Herrenschmidt
2007-11-14 9:20 ` Gerhard Pircher
2007-11-13 23:23 ` Dan Malek
2007-11-13 23:39 ` Olof Johansson
2007-11-13 23:53 ` Jon Smirl
2007-11-14 1:17 ` Benjamin Herrenschmidt
2007-11-14 1:32 ` Jon Smirl
2007-11-15 1:35 ` Jerry Van Baren
2007-11-15 2:34 ` Jon Smirl
2007-11-18 0:47 ` Wolfgang Denk
2007-11-22 23:37 ` Benjamin Herrenschmidt [this message]
2007-11-23 0:00 ` Jon Smirl
2007-11-23 0:22 ` Benjamin Herrenschmidt
2007-11-23 15:03 ` Jon Smirl
2007-11-23 20:26 ` Jon Smirl
2007-11-23 20:30 ` Grant Likely
2007-11-13 22:03 ` Jon Smirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1195774625.6970.145.camel@pasglop \
--to=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=olof@lixom$(echo .)net \
--cc=wd@denx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox