From: "Jeff Domogala" <jdomogala@acmepacket.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: PowerPC MMU questions
Date: Thu, 11 Nov 2004 22:36:23 -0500 [thread overview]
Message-ID: <NFBBJCNFKLFMBACPKDKCCEANELAA.jdomogala@acmepacket.com> (raw)
In-Reply-To: <20041111211549.3B221C14B3@atlas.denx.de>
Folks,
I am dealing with a PowerPC 7455. Here is my understanding regarding the
MMU translation order: If the address is covered in a BAT, that BAT
translation is in effect. If there is no BAT entry, then the page tables
are used to translate the address. If there is no page table entry, an
exception is thrown and the exception handler for the miss needs to add a
new PTE. So, correct me if I'm wrong in my translation.
Now, The system starts up with BAT entries to get the system off the ground.
I have equivalent BAT entries for the instruction and data sides. I also
have the L1 I and D caches on as well as the L2 cache (I and D mode). The
reason for using the BATs is to create non-cached I/O regions until the MMU
PTEs are populated. Once the MMU PTEs are setup, the caches are flsuhed and
disabled, the MMU is disabled, the BATS disabled, the MMU re-enabled and the
caches re-enabled. So here are my questions:
1. Is it ok to have the same I and D BAT entries?
2. Is it ok to setup the initial MMU PTEs with the BATs enabled or should
the caches be disabled and MMU disabled during the PTE setup?
3. Is there some other esource out there (mailing list or otherwise) that I
should be addressing these questions to?
Thanks,
Jeff Domogala
next prev parent reply other threads:[~2004-11-12 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 12:42 Which board is similar to mine, and how do I build a custom config? Peter Asemann
2004-11-11 21:15 ` Wolfgang Denk
2004-11-12 3:36 ` Jeff Domogala [this message]
2004-11-12 16:01 ` PowerPC MMU questions Kumar Gala
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=NFBBJCNFKLFMBACPKDKCCEANELAA.jdomogala@acmepacket.com \
--to=jdomogala@acmepacket.com \
--cc=linuxppc-embedded@ozlabs.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