From: "G. Guivel" <gguevel@interfaceconcept.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: MMU problems on MPC860P
Date: Tue, 19 Sep 2000 19:51:04 +0200 [thread overview]
Message-ID: <000001c02262$42c4b160$2901a8c0@none> (raw)
Dan wrote:
> You may just want to hop over to the MontaVista web site and use the
2.2.14 kernel from CDK 1.2.
I made a new kernel from cllf(rpxclassic) board with MPC860T.
I have the same problems than with the 2.2.13 kernel.
It seems that Linux does not clear all mmu registers.
Which registers must be cleared by the previous monitor ?
I use my personal monitor which does not deal with mmu.
I don't know if EPPC-BUG makes some special actions before
loading Linux loader.
If you have some idea.
Thanks
Gerard
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-09-19 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-19 17:51 G. Guivel [this message]
2000-09-19 22:15 ` MMU problems on MPC860P Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-09-28 14:28 Girard Guivel
2000-09-15 16:40 G. Guével
2000-09-15 17:19 ` 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='000001c02262$42c4b160$2901a8c0@none' \
--to=gguevel@interfaceconcept.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).