From: Dan Malek <dan@embeddededge.com>
To: Mikko Alutoin <mikko.alutoin@luukku.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problem with MMU again
Date: Fri, 26 Mar 2004 11:45:40 -0500 [thread overview]
Message-ID: <40645E34.6000202@embeddededge.com> (raw)
In-Reply-To: 1080318719206.mikko.alutoin.17604.2qSxXdx65WQeg1tDzWIhzQ@luukku.com
Mikko Alutoin wrote:
> I am confused. How come the boot code now fails to get the MMU working,
You are chasing ghosts. There is nothing wrong with the MMU initialization.
There are just times during the initialization that the system and the BDI2000
are not exactly in sync. This is one of them.
Let the code run, do some post-mortem debugging (like dumping out the
console log buffer for starters). Work backward from the failure instead
of trying to step into it (pun intended) :-)
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-26 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 16:31 Problem with MMU again Mikko Alutoin
2004-03-26 16:45 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-27 13:05 Mikko Alutoin
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=40645E34.6000202@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mikko.alutoin@luukku.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).