From: Dan Malek <dan@embeddededge.com>
To: "Gessner, Matt" <mattg@aiinet.com>
Cc: "'Linux PPC'" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: BDI2000 and failed MMU translations
Date: Wed, 23 Jan 2002 17:51:10 -0500 [thread overview]
Message-ID: <3C4F3E5E.80805@embeddededge.com> (raw)
In-Reply-To: 638AA0336D7ED411928700D0B7B0D75BB32414@mail2.aiinet.com
Gessner, Matt wrote:
> It's straight 2_4. I wasn't stopping at start_kernel though.
You don't need to stop anywhere unless there are some breakpoints
you want to set for early debug.
> I don't have PTBASE set up.
You need:
MMU XLAT 0xc0000000
PTBASE 0x000000f0
The newer kernels initialize the page table pointers for the BDI2000,
so ignore comments about stopping and setting values. We went through
several iterations of implementation, so anything written about how to
do this manually is probably wrong :-).
> ...... I'm going to
> break at start kernel FIRST, then connect with BDI, then
> see if I can look at my data.
How do you break and then connect the BDI? You need the BDI
connected to set and trap the breakpoint.
Have fun.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-23 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 22:22 BDI2000 and failed MMU translations Gessner, Matt
2002-01-23 22:51 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-23 22:58 Gessner, Matt
2002-01-23 23:34 ` Dan Malek
2002-01-23 22:57 Gessner, Matt
2002-01-23 22:55 Gessner, Matt
2002-01-23 22:44 Rudolf Ladyzhenskii
2002-01-23 22:08 Gessner, Matt
2002-01-23 22:23 ` Dan Malek
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=3C4F3E5E.80805@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mattg@aiinet.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).