From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace•com>
To: "Morrison, Tom" <tmorrison@empirix•com>
Cc: linuxppc-dev@ozlabs•org, linuxppc-embedded@ozlabs•org
Subject: Re: device tree / how to build/compile & use with u-boot to boot uImage?
Date: Fri, 09 Feb 2007 17:25:51 -0500 [thread overview]
Message-ID: <45CCF4EF.9050507@smiths-aerospace.com> (raw)
In-Reply-To: <BD261180E6D35F4D9D32F3E44FD3D901066B2252@EMPBEDEX.empirix.com>
Morrison, Tom wrote:
> All,
>
> Sorry for my ignorance here, but we have upgraded our kernel from
> 2.6.11.xx to 2.6.20-rcx (using a specific git-branch for the mpc85xx)
> to run on the MPC8548CDS eval board (using default options provided
> by this branch for this eval board). I successfully compiled/loaded the
> uImage, but it hangs after decompression (with root=/dev/nfs)
>
> Also, I was told to upgrade our u-boot source code (with another git
> branch for to the mpc85xx) and successfully get to the u-boot prompt.
>
> From googling through the lists - it seems that I need to build a
> device tree blob and pass that device tree to the kernel in some
> fashion?
>
> I tried to compile the default dts image (using the dtc compiler
> installed by LTIB), but it is complaining about no '/chosen' in
> the definition:
>
> <path>/dtc -I dts -O dtb - -o mpc8548cds.dtb -V 16 dts/mpc8548cds.dts
Trivia: the no "/chosen" warning can be ignored. The u-boot command
"bootm" generates the "/chosen" branch when you run the command and it
boots linux.
Note: You want version 16 (or better?) for the fdt blob. I believe the
dtc defaults to this now, but it wasn't always that way.
[snip - others have chimed in]
> Tom Morrison
> Principal Software Engineer
gvb
next prev parent reply other threads:[~2007-02-09 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 21:55 device tree / how to build/compile & use with u-boot to boot uImage? Morrison, Tom
2007-02-09 22:19 ` Ben Warren
2007-02-09 22:25 ` Jerry Van Baren [this message]
2007-02-09 22:41 ` David Gibson
2007-02-09 22:37 ` Grant Likely
2007-02-10 0:42 ` David Gibson
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=45CCF4EF.9050507@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=tmorrison@empirix$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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