From: Dan Malek <dan@mvista.com>
To: Freddy Lugo <wilflugo@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Can not access memory after turning MMU on
Date: Mon, 07 May 2001 18:00:32 -0400 [thread overview]
Message-ID: <3AF71B00.E3FCEA37@mvista.com> (raw)
In-Reply-To: 20010507204100.56613.qmail@web9901.mail.yahoo.com
Freddy Lugo wrote:
> This register exists or has its counterpart on the
> MPC750? Besides the DER value, there are other
> methods to work and find the problem?
You are way, way, way lost...........You can't be building MPC8xx
code and expecting it to run on the 750. You need to select a
kernel configuration that enables 6xx/7xx/74xx processors and
a CHRP reference design.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-05-07 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 20:41 Can not access memory after turning MMU on Freddy Lugo
2001-05-07 20:56 ` Paul White
2001-05-07 22:00 ` Dan Malek [this message]
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=3AF71B00.E3FCEA37@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wilflugo@yahoo.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).