From: Jon Loeliger <jdl@freescale.com>
To: mike zheng <mail4mz@gmail.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: System crash on boot_e500.S
Date: Tue, 14 Aug 2007 15:40:14 -0500 [thread overview]
Message-ID: <1187124014.32650.80.camel@ld0161-tx32> (raw)
In-Reply-To: <5c9cd53b0708141314o57440c62waffb4cca3f2be0b9@mail.gmail.com>
On Tue, 2007-08-14 at 15:14, mike zheng wrote:
> Hi All,
>
> I am trying to bring up MPC8548 CDS board on 2.4 kernel. I have
> problem in the head
Ow, it hurts when I do this!
> _e500.S. The "mtspr SRR0, r7; mtspr SRR1 r6" does not work for me. The
> content of R7 and R6 are not moved to SRR0 and SRR1. I am using the
> tool-chain from Freescale for 2.6 kernel.
>
> Any idea on this issue?
Maybe use current 2.6 code?
jdl
next prev parent reply other threads:[~2007-08-14 20:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 20:14 System crash on boot_e500.S mike zheng
2007-08-14 20:40 ` Jon Loeliger [this message]
2007-08-15 13:57 ` mike zheng
2007-08-15 16:02 ` Scott Wood
2007-08-15 16:28 ` Kumar Gala
2007-08-15 16:30 ` Scott Wood
2007-08-15 16:41 ` Becky Bruce
2007-08-15 20:53 ` mike zheng
2007-08-15 20:57 ` Scott Wood
2007-08-15 21:23 ` mike zheng
2007-08-16 7:15 ` Geert Uytterhoeven
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=1187124014.32650.80.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mail4mz@gmail.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).