From: Wolfgang Denk <wd@denx.de>
To: "Williams, Kevin M." <kevin.m.williams@marconi.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Abatron BDI2000
Date: Tue, 20 Nov 2001 18:13:15 +0100 [thread overview]
Message-ID: <20011120171320.8601DF9B9@denx.denx.de> (raw)
In-Reply-To: Your message of "Tue, 20 Nov 2001 11:36:40 EST." <A3E34B558F5CD211B4980008C7A4A99003C5853A@sparrow.gso.mcs.marconi.com>
Dear Kevin,
in message <A3E34B558F5CD211B4980008C7A4A99003C5853A@sparrow.gso.mcs.marconi.com> you wrote:
>
> I just received a BDI2000 and it works great for debugging my bootrom, but
> I'm a little confused about settings to use for debugging the
> kernel...seeing a working example should be enough to get me going.
Oops??? The config file for the BDI2000 depends on the processor
architecture and board used, but that's it. You can use the SAME
config file both for firmware and for Linux kernel debugging.
Make sure you've RTFM about the "MMU XLAT" and the "PTBASE" settings.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Computers are not intelligent. They only think they are.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-20 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 16:36 Abatron BDI2000 Williams, Kevin M.
2001-11-20 17:13 ` Wolfgang Denk [this message]
[not found] ` <3BFA8C23.465CD6B1@cambridgebroadband.com>
2001-11-21 1:07 ` Michael Habermann
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 18:04 Williams, Kevin M.
2001-11-20 18:54 ` Wolfgang Denk
2001-11-02 15:55 Joshua Horvath
2001-11-02 18:10 ` Scott Anderson
2001-11-02 21:03 ` Wolfgang Denk
2001-01-31 0:37 Brian Kuschak
2001-01-30 22:42 Brian Kuschak
2001-01-31 0:13 ` Wolfgang Denk
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=20011120171320.8601DF9B9@denx.denx.de \
--to=wd@denx.de \
--cc=kevin.m.williams@marconi.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).