From: Matthew McClintock <msm@freescale.com>
To: Li Yang <LeoLi@freescale.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [RFC] New target 'cuImage' - compatibility uImage
Date: Thu, 03 Aug 2006 11:24:06 -0500 [thread overview]
Message-ID: <1154622246.5094.18.camel@localhost> (raw)
In-Reply-To: <a0bc9bf80608030917y7fde2b75n6719dc675cad8cfe@mail.gmail.com>
On Fri, 2006-08-04 at 00:17 +0800, Li Yang wrote:
>
> Though it will need more space, the increase won't be too much as
> wrapper and FDT should be very small. The benefit is that kernel can
> be extract directly to it's destination(address 0), rather than
> extract to another place and then move it there. A classical
> time/space tradeoff.
>
I'm not sure that is correct. Let me walk through the steps to verify.
1) Load cuImage at a load address
2) Extract zImage at an address and begin execution
3) Copy kernel to load address and fixup DTB, etc.
4) Start kernel execution
versus...
1) Load cuImage at a load address
2) Copy zImage to an address and begin execution
3) Extract kernel to load address and fixup DTB, etc.
4) Start kernel execution
There will always be that extra copy in there vs. just running the
zImage itself. This is to maintain compatibility with older u-boots,
which is the main point of this target.
Am I missing something here?
-Matthew
next prev parent reply other threads:[~2006-08-03 16:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 20:59 [RFC] New target 'cuImage' - compatibility uImage 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 9:29 Milton Miller
2006-08-03 18:17 Milton Miller
2006-08-03 18:53 ` 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=1154622246.5094.18.camel@localhost \
--to=msm@freescale.com \
--cc=LeoLi@freescale.com \
--cc=Linuxppc-dev@ozlabs.org \
/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).