From: "Greg Griffes" <ggg@ieee.org>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: 7400 mmu_init problem
Date: Fri, 5 Apr 2002 05:45:08 -0500 [thread overview]
Message-ID: <00e101c1dc8e$f4f8d720$6401a8c0@attbi.com> (raw)
Hello,
I am trying to port linuxppc_2_4_devel to a custom 750 design.
Using the GNU binutils and gcc-core-2.95.3 tools.
After ppc_md.progress reports "MMU: exit" in mm/init.c::mmu_init()
the kernel goes into panic() and dies there.
I have been using a lousy, unreliable JTAG debugger. Today, I have a
BDI2000 and will be learning how to use it and GDB :-))
Has anyone experienced this in the past?
Does anyone have a rough idea of the cause of the problem?
My guess is that it could be many possible problems, but, it has to
be something that I did wrong in <my>_setup.c I haven't changed
much in the kernel itself.
The low level IO is mapped at 0xEC00_0000; could that be a problem?
The kernel is configured very slim, could I be excluding necessary
functionality?
Thanks for listening,
Greg Griffes
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-04-05 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 10:45 Greg Griffes [this message]
2002-04-05 17:28 ` 7400 mmu_init problem Matt Porter
2002-04-07 0:47 ` Greg Griffes
2002-04-07 4:53 ` Matt Porter
2002-04-07 8:08 ` Wolfgang Denk
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='00e101c1dc8e$f4f8d720$6401a8c0@attbi.com' \
--to=ggg@ieee.org \
--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).