From: Scott Wood <scottwood@freescale.com>
To: Wolfgang Denk <wd@denx.de>
Cc: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: mpc 860 boot linux2.6.23 problem
Date: Tue, 16 Oct 2007 11:18:23 -0500 [thread overview]
Message-ID: <4714E44F.7030909@freescale.com> (raw)
In-Reply-To: <20071015233839.959F4247BB@gemini.denx.de>
Wolfgang Denk wrote:
> In message <4713A08C.3060204@freescale.com> you wrote:
>> keng_629 wrote:
>>>
>>> i am proting linux2.63.23 to mpc860t board with uboot1.1.4 as bootloader.
>>> my bootargs is root=/dev/ram rw init=/linuxrc.
>>> i use debugger to see the regedits, find pc is run in the cpu_idle().
>>> what is wrong with my kernel, plese give me some advice.thank you .
>> Posting the same thing over and over again isn't going to change the
>> response. Try head-of-Linus's-git, make sure you're using arch/powerpc,
>> and post the device tree you're using. Without more information, we
>> can't help you.
>
> Just to point out the obvious: U-Boot 1.1.4 is *way* too old to
> support any device-tree based kernel, so the fist step is to update
> U-Boot to a somewhat recent version (i. e. 1.3.0-rcX).
Upgrading to the latest u-boot certainly shouldn't hurt, but I don't
think there's any device tree support for 8xx yet, so for now he should
boot with cuImage.
-Scott
next prev parent reply other threads:[~2007-10-16 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 3:15 mpc 860 boot linux2.6.23 problem keng_629
2007-10-15 17:17 ` Scott Wood
2007-10-15 23:38 ` Wolfgang Denk
2007-10-16 16:18 ` Scott Wood [this message]
2007-10-17 2:58 ` Dan Malek
2007-10-17 15:31 ` Scott Wood
2007-10-17 16:40 ` Dan Malek
2007-10-17 17:26 ` Scott Wood
[not found] ` <200710190724253750363@126.com>
2007-10-21 13:43 ` keng_629
2007-10-17 18:54 ` Jochen Friedrich
2007-10-17 19:15 ` Scott Wood
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=4714E44F.7030909@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/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).