From: Matthew McClintock <msm@freescale.com>
To: Milton Miller <miltonm@bga.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: [RFC] New target 'cuImage' - compatibility uImage
Date: Thu, 03 Aug 2006 13:53:28 -0500 [thread overview]
Message-ID: <1154631208.5094.25.camel@localhost> (raw)
In-Reply-To: <3115462902741b71efb4.2044897763.miltonm@bga.com>
On Thu, 2006-08-03 at 13:17 -0500, Milton Miller wrote:
> On Thu Aug 3 2006 10:30:13 AM CDT, Matthew McClintock wrote:
> > On Thu, 2006-08-03 at 04:47 -0700, Li Yang-r58472 wrote:
> > > If my understanding to Matt's idea is correct, it will be a good way,
> > > IMHO. How about use the naming of uwImage(U-boot Wrapped Image) or
> > > utImage(u-boot device-Tree Image).
> >
> > I am completely open to a better name. Anyone else care to share their
> > opinion?
>
> Do newer versions of uboot support device tree kernels directly? If not, then
> I would say make this uimage. Otherwise, I would say uzImage unless we
> decide to call the wrapper that adds the tree something else, like uImage.dt.
>
> Or maybe its uImage and config vars say which it is.
>
There is an unofficial way to boot device tree kernels directly from
U-Boot. There was an older method that has been in U-Boot a long time
(and still is), however I just submitted a series of patches which
updates that method.
As far as I know the new method is liked better by Wolfgang, so maybe he
will start accepted board patches based on my work? Either way, for
boards with newer U-Boots (at some point) will not boot using this
method.
Wolfgang, care to comment?
-Matthew
next prev parent reply other threads:[~2006-08-03 18:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 18:17 [RFC] New target 'cuImage' - compatibility uImage Milton Miller
2006-08-03 18:53 ` Matthew McClintock [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 9:29 Milton Miller
2006-08-02 20:59 Matthew McClintock
2006-08-02 22:33 ` Wolfgang Denk
2006-08-03 11:38 ` Li Yang-r58472
2006-08-03 15:29 ` Matthew McClintock
2006-08-03 15:56 ` Li Yang
2006-08-03 16:02 ` Matthew McClintock
2006-08-03 16:17 ` Li Yang
2006-08-03 16:24 ` Matthew McClintock
2006-08-03 16:47 ` Li Yang
2006-08-03 20:14 ` Wolfgang Denk
2006-08-03 20:20 ` Matthew McClintock
2006-08-03 20:25 ` Wolfgang Denk
2006-08-03 20:40 ` Matthew McClintock
2006-08-03 20:07 ` Wolfgang Denk
2006-08-03 19:37 ` Mark A. Greer
2006-08-03 20:02 ` Wolfgang Denk
2006-08-03 20:00 ` Wolfgang Denk
2006-08-03 20:12 ` Matthew McClintock
2006-08-03 20:23 ` Wolfgang Denk
2006-08-03 20:31 ` Matthew McClintock
2006-08-03 0:30 ` Tom Rini
2006-08-03 15:24 ` Matthew McClintock
2006-08-03 11:47 ` Li Yang-r58472
2006-08-03 15:30 ` Matthew McClintock
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=1154631208.5094.25.camel@localhost \
--to=msm@freescale.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.