From: David Gibson <david@gibson.dropbear.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org,
Sebastian Siewior <linuxppc-embedded@ml.breakpoint.cc>
Subject: Re: boot cuImage on an old u-boot
Date: Mon, 25 Aug 2008 19:36:17 +1000 [thread overview]
Message-ID: <20080825093617.GA1619@yookeroo.seuss> (raw)
In-Reply-To: <20080821161505.GA15669@ld0162-tx32.am.freescale.net>
On Thu, Aug 21, 2008 at 11:15:05AM -0500, Scott Wood wrote:
> On Wed, Aug 20, 2008 at 05:09:58PM +0200, Sebastian Siewior wrote:
> > I have here a mpc8540ads board and a u-boot 1.0.0. I've build the
> > defconfig for the board and I tried to boot the genarated
> > cuImage.mpc8540ads image. After the bootm command I see just
> >
> > |8540> bootm 1000000
> > |## Booting image at 01000000 ...
> > | Image Name: Linux-2.6.26
> > | Image Type: PowerPC Linux Kernel Image (gzip compressed)
> > | Data Size: 1232711 Bytes = 1.2 MB
> > | Load Address: 00400000
> > | Entry Point: 004005ac
> > | Verifying Checksum ... OK
> > | Uncompressing Kernel Image ... OK
> > |
> >
> > I don't see the device tree fixups printfs, so crash happend quite
> > early. Anyone an idea what I could have done wrong?
>
> Make sure the device tree contains /chosen/linux,stdout-path.
No paths to properties, remember!
Make sure the device tree contains a linux,stdout-path property in
/chosen.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2008-08-25 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 15:09 boot cuImage on an old u-boot Sebastian Siewior
2008-08-21 16:15 ` Scott Wood
2008-08-25 9:36 ` David Gibson [this message]
2008-09-12 15:31 ` Sebastian Siewior
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=20080825093617.GA1619@yookeroo.seuss \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ml.breakpoint.cc \
--cc=scottwood@freescale.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).