From: Scott Wood <scottwood@freescale•com>
To: Mike Timmons <mike_timmons@trimble•com>
Cc: Stephen Horton <SHorton@kodiaknetworks•com>,
linuxppc-embedded@ozlabs•org
Subject: Re: Problem with cuImage Linux entry from old U-boot
Date: Tue, 22 Jul 2008 13:20:30 -0500 [thread overview]
Message-ID: <488624EE.9040502@freescale.com> (raw)
In-Reply-To: <161B3BAD77161449A144FF054231C3D60249D825@uss-am-xch-01.am.trimblecorp.net>
Mike Timmons wrote:
> Related question: I'm using a newer U-boot and managing the load of the
> kernel and the device tree from separate partitions of my boot media.
>
> Having the two partitions and managing the kernel and the tree
> separately is a bit cumbersome, or maybe I'm just lazy. Regardless, can
> I just use that "static" file name option when I build the kernel, load
> the cuImage, and just invoke
>
> bootm <cuImageLoadAddress> ?
>
> Will it work to just leave off the - <device tree Ram address>
>
> I think I had it set-p right yesterday and I gave it a try, but no joy.
>
> Can it be this simple to statically link the device tree with the kernel
> build? For my application I don't see a benefit in keeping them separate
> (the kernel and the tree).
Yes, you can use cuImage to bundle the device tree with the kernel (note
that the type of image you use *must* match the type of bootm command
you use), though it's not recommended if you have a u-boot that can
properly pass a device tree. cuImage relies on the bd_t to get
information from u-boot, and this is a very fragile structure, and
contains less information than the device tree.
-Scott
next prev parent reply other threads:[~2008-07-22 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 20:39 Problem with cuImage Linux entry from old U-boot Stephen Horton
2008-07-22 18:05 ` Scott Wood
2008-07-22 18:13 ` Mike Timmons
2008-07-22 18:20 ` Scott Wood [this message]
2008-07-22 19:23 ` Stephen Horton
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=488624EE.9040502@freescale.com \
--to=scottwood@freescale$(echo .)com \
--cc=SHorton@kodiaknetworks$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=mike_timmons@trimble$(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