From: Nicolas Pohland <pohland@snom.de>
To: linuxppc-dev@lists.linuxppc.org
Cc: devel@gate.crashing.org
Subject: MMU Initialization Problem
Date: Tue, 09 Nov 1999 14:11:27 +0100 [thread overview]
Message-ID: <38281D7F.CC9914C@snom.de> (raw)
Hi Mark,
I have the same problem on a FADS board and 2.3.10. I do not have a
solution yet, but maybe able to describe the
problem in more detail.
I can unzip the kernel at location 0 and then this space is mapped to
0xc0000000 in 1 8Mb page.
Then the start_here routine and in it the MMU_init function called.
This is what I found strange:
a. The level 1 descriptors in the table are made up of effective
addresses (or virtual) and
NOT of physical addresses.
b. The valid bit (LSB) of the descriptor is not set to 1.
Have I missed something here ?
Ciao,
Nicolas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-11-09 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-09 13:11 Nicolas Pohland [this message]
1999-11-09 19:36 ` MMU Initialization Problem 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=38281D7F.CC9914C@snom.de \
--to=pohland@snom.de \
--cc=devel@gate.crashing.org \
--cc=linuxppc-dev@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).