From: Wolfgang Denk <wd@denx.de>
To: greyham@research.canon.com.au (Graham Stoney)
Cc: ron.flory@adtran.com (Ron Flory),
kharris@nexus-tech.net (Kyle Harris),
linuxppc-embedded@lists.linuxppc.org
Subject: Re: BDM recommendations
Date: Mon, 30 Oct 2000 09:51:20 +0100 [thread overview]
Message-ID: <200010300851.e9U8pKo12926@denx.local.net> (raw)
In-Reply-To: Your message of "Mon, 30 Oct 2000 11:01:32 +1100." <20001030000132.C1A904FF2B@brixi.research.canon.com.au>
In message <20001030000132.C1A904FF2B@brixi.research.canon.com.au>
Graham Stoney wrote:
> Ron Flory writes:
> > couldn't find that one, it seems to live here now...
> >
> > http://sourceforge.net/projects/bdm4gdb/
>
> There's no content there though, which is why there's no pointer to it in the
> HOWTO. Try the MPCBDM site at:
> http://www.vas-gmbh.de/software/mpcbdm/
This is the *old* project, which has seen major changes since.
I don't really understand this: both
http://bdm4gdb.sourceforge.net/
[which introduces the BDM4GDB Interface Project] and
http://sourceforge.net/projects/bdm4gdb/
[the "official" project home page] work fine for me.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Real programmers don't comment their code. It was hard to write, it
should be hard to understand.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-30 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39F97906.14B7CCF6@adtran.com>
2000-10-30 0:01 ` BDM recommendations Graham Stoney
2000-10-30 8:51 ` Wolfgang Denk [this message]
2000-10-26 17:38 Kyle Harris
2000-10-26 18:57 ` Matt Porter
2000-10-26 19:27 ` Wolfgang Denk
2000-10-27 0:34 ` Eurico Inocencio
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=200010300851.e9U8pKo12926@denx.local.net \
--to=wd@denx.de \
--cc=greyham@research.canon.com.au \
--cc=kharris@nexus-tech.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ron.flory@adtran.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).