From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Tomasz Figa <t.figa@samsung.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
linux-samsung-soc@vger.kernel.org, linux@arm.linux.org.uk,
devicetree-discuss@lists.ozlabs.org, kgene.kim@samsung.com,
thomas.abraham@linaro.org, bones@secretlab.ca,
linux-arm-kernel@lists.infradead.org
Subject: $(make uImage) is stupid [Was: Re: Early kernel hang with big DTB appended]
Date: Mon, 14 Jan 2013 09:45:24 +0100 [thread overview]
Message-ID: <20130114084524.GN14860@pengutronix.de> (raw)
In-Reply-To: <35730055.SShm3zF9mO@amdc1227>
Hello,
unrelated to the original problem ...
On Fri, Jan 04, 2013 at 11:18:56AM +0100, Tomasz Figa wrote:
> We are using uImages built with same parameters as those used in simple
> 'make uImage', just with a DTB appended to zImage before running mkimage
> on it.
note that the parameters used for $(make uImage) are not optimal, only
safe. They use (letting the MMU aside) the link address of the final
image as load address. That means as U-Boot probably didn't choose the
right address when reading the image it has to move it to the link
address and then jumps into it. Then the decompressor notices that the
compressed image is located where the decompressed image should go to
and so has to move the image again.
So you could save quite some time during boot if you'd teach U-Boot that
it can just use the image where it was loaded to.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-01-14 8:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 15:55 Early kernel hang with big DTB appended Tomasz Figa
2013-01-03 18:40 ` Bryan Evenson
2013-01-04 10:26 ` Tomasz Figa
2013-01-04 2:48 ` Nicolas Pitre
2013-01-04 10:18 ` Tomasz Figa
2013-01-14 8:45 ` Uwe Kleine-König [this message]
2013-01-11 16:45 ` Sascha Hauer
2013-01-14 22:13 ` Nicolas Pitre
2013-01-15 10:53 ` Sascha Hauer
2013-01-15 11:26 ` Tomasz Figa
2013-01-15 18:12 ` Nicolas Pitre
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=20130114084524.GN14860@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=bones@secretlab.ca \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.pitre@linaro.org \
--cc=t.figa@samsung.com \
--cc=thomas.abraham@linaro.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).