From: andre@bluewatersys•com (Andre Renaud)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] ARM: Add Kconfig option to use mkimage -T kernel_noload
Date: Thu, 01 Mar 2012 11:28:33 +1300 [thread overview]
Message-ID: <4F4EA691.9040406@bluewatersys.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17BDDF21A1@HQMAIL01.nvidia.com>
On 01/03/12 10:27, Stephen Warren wrote:
> Russell King wrote at Wednesday, February 29, 2012 1:45 PM:
> ...
>> So, really, comparing a standard uImage produced by the standard kernel
>> with gzipped Image is far from a fair comparison. And that's actually
>> another argument for getting rid of the uImage target... it may make
>> people think a bit about what they're doing rather than accepting
>> whatever default location someone else chose for their kernel.
>
> That seems like more of an argument for making the uImage target use
> -T kernel_noload unconditionally, rather than removing the target.
> Since doing so would solve the issue about the kernel picking a load
> address.
>
> That is, ignoring any arguments about breaking existing workflows at
> least...
I think this is the case that I was seeing - the current behaviour of
the uImage target, of using the zreladdr as the load/start addresses
essentially guarantees the worst case relocation behaviour.
Regards,
Andre
next prev parent reply other threads:[~2012-02-29 22:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 0:03 [PATCH 1/2] ARM: Add Kconfig option to use mkimage -T kernel_noload Stephen Warren
2012-02-29 0:03 ` [PATCH 2/2] ARM: tegra: Add zreladdr etc to Makefile.boot for Tegra30 Stephen Warren
2012-02-29 12:29 ` [PATCH 1/2] ARM: Add Kconfig option to use mkimage -T kernel_noload Jean-Christophe PLAGNIOL-VILLARD
2012-02-29 16:58 ` Stephen Warren
2012-02-29 18:14 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-29 18:33 ` Tim Bird
2012-02-29 18:50 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-12 17:40 ` Marek Vasut
2012-03-12 17:44 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-29 19:12 ` Uwe Kleine-König
2012-02-29 19:17 ` Stephen Warren
2012-02-29 19:44 ` Uwe Kleine-König
2012-02-29 19:59 ` Stephen Warren
2012-02-29 20:12 ` Andre Renaud
2012-02-29 20:16 ` Stephen Warren
2012-02-29 20:19 ` Russell King - ARM Linux
2012-02-29 20:25 ` Andre Renaud
2012-02-29 20:29 ` Russell King - ARM Linux
2012-02-29 20:39 ` Uwe Kleine-König
2012-02-29 20:45 ` Russell King - ARM Linux
2012-02-29 20:59 ` Uwe Kleine-König
2012-03-01 4:55 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-12 17:42 ` Marek Vasut
2012-02-29 21:27 ` Stephen Warren
2012-02-29 22:28 ` Andre Renaud [this message]
2012-02-29 20:30 ` Uwe Kleine-König
2012-02-29 23:53 ` Ryan Mallon
2012-03-12 17:44 ` Marek Vasut
2012-03-01 15:34 ` Mark Brown
2012-03-01 17:01 ` Stephen Warren
2012-03-05 4:21 ` Olof Johansson
2012-03-05 20:29 ` 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=4F4EA691.9040406@bluewatersys.com \
--to=andre@bluewatersys$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/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