From: Scott Wood <scottwood@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: Wed, 15 Aug 2007 15:57:53 -0500 [thread overview]
Message-ID: <46C368D1.7000403@freescale.com> (raw)
In-Reply-To: <5c9cd53b0708151353u67e10e03lf12c3971e4f3d63@mail.gmail.com>
mike zheng wrote:
> Unfortunately, all the applications are running on 2.4 kernel. I can not
> just throw the 2.4 kernel.
And in what way does 2.6 break these applications?
> I took the some core specific code from
> ppc.bkbits.net, such as head_e500.S and mpc85xx_cds_common.c. I assume the
> image should work on the 8548 CDS board, or at least for the bootup. I shall
> able to have the serial port working in platform_init(). However , the
> code stops in the head_e500.S. This does not make any sense. Please correct
> me if I am wrong.
Of course it makes sense -- you can't just go around ripping random
files from a codebase, sticking them in a version from several years
earlier, and expecting it to "just work".
> Any suggest or comment is welcome, I am struggling with this issue for
> almost one week...... :-(
How long would you have struggled with getting your applications running
on a more recent kernel instead?
-Scott
next prev parent reply other threads:[~2007-08-15 20:58 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
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 [this message]
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=46C368D1.7000403@freescale.com \
--to=scottwood@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).