From: "machael thailer" <dony.he@huawei.com>
To: "Zehetbauer Thomas" <TZ@link.topcall.co.at>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Uncompress Ok, but cannot run linux kernel...
Date: Tue, 8 May 2001 19:51:37 +0800 [thread overview]
Message-ID: <001901c0d7b5$426f0b80$8021690a@huawei.com> (raw)
In-Reply-To: 41EA756DBC9FD0118CFC0020AFDB5C5A188DC9@tcint1ntsrv
>
> I stumbled into the same problem a while ago.
>
> While I did not use a hardware debugger I used the sample demonstrating
> serial output to find that the Montavista kernel stops at the rfi
> instruction which is used to simultanoeusly turn on instruction and data
> address translation and to set the instruction pointer to the (remapped)
> start_here label. Unfortunately I lost my PPC hardware (405GP Walnut
> board) before I could find any solution.
Yes, this is also exactly what i meet now.
I find that "turn_on_mmu" use SYNC as following:
turn_on_mmu:
.....
SYNC
RFI
here SYNC may do nothing according to your .config(CONFIG_PPC601_SYNC_FIX)
if you look into arch/ppc/kernel/ppc_asm.h.
Will this be a problem? I use linux-2.4.2 .
machael
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-08 11:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 10:43 Uncompress Ok, but cannot run linux kernel Zehetbauer Thomas
2001-05-08 11:51 ` machael thailer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 3:40 machael thailer
2001-05-10 4:16 ` Paul White
[not found] <439B3F1E9095D41193DE00D0B74FF30601CE7900@xpr01.prd.hp.com>
2001-05-08 13:50 ` Freddy Lugo
2001-05-08 15:21 ` Wolfgang Denk
2001-05-08 21:21 ` Freddy Lugo
2001-05-06 1:01 machael thailer
2001-05-07 19:10 ` Dan Malek
2001-05-08 1:36 ` machael thailer
2001-05-10 3:08 ` machael thailer
2001-05-10 10:45 ` Matt Porter
2001-05-08 0:58 ` Michael Habermann
2001-05-08 1:16 ` Dan Malek
2001-05-08 8:02 ` Michael Habermann
2001-05-08 8:06 ` machael thailer
2001-05-08 8:43 ` Wolfgang Denk
2001-05-08 10:06 ` machael thailer
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='001901c0d7b5$426f0b80$8021690a@huawei.com' \
--to=dony.he@huawei.com \
--cc=TZ@link.topcall.co.at \
--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).