From: Bob Beck <beck@assurtech.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: MMU Problem bringing up kernel with PPC 603 chip
Date: 27 Feb 2004 11:23:13 +1400 [thread overview]
Message-ID: <1077830593.4199.7.camel@budweiser> (raw)
In-Reply-To: <20040227103636.78365C0655@atlas.denx.de>
All,
I'm bringing up my 1st kernel on a proprietary board
using a PPC 603E chip.
The kernel is configured using the 6xx/7xx ppc selection.
The kernel starts executing at __start in head.S and
branches to early_init(). I have stubbed out the call
to prom_init() since this is an embedded system and
not a power mac (as the comments at the top of the
prom.c file indicate).
The code returns to head.S and branches to mmu_off.
Here is the code for mmu_off.
mmu_off:
addi r4, r3, __after_mmu_off - _start
mfmsr r3
andi. r0,r3,MSR_DR|MSR_IR /* MMU enabled? */
beqlr
andc r3,r3,r0
mtspr SRR0,r4
mtspr SRR1,r3
sync
RFI
This executes all the way to the "RFI" instruction,
but never comes back to the place in the code that
called mmu_off.
Why is the "return from interrupt" going out into
space ? Any suggestions ?
Best Regards,
Bob Beck
beck@assurtech.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-26 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 10:11 problem with standard libc on 8xx Demke, Torsten
2004-02-27 10:36 ` Wolfgang Denk
2004-02-26 21:23 ` Bob Beck [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-27 17:19 MMU Problem bringing up kernel with PPC 603 chip VanBaren, Gerald (AGRE)
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=1077830593.4199.7.camel@budweiser \
--to=beck@assurtech.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).