From: tim.bird@am•sony.com (Tim Bird)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] ARM: Add Kconfig option to use mkimage -T kernel_noload
Date: Wed, 29 Feb 2012 10:33:58 -0800 [thread overview]
Message-ID: <4F4E6F96.8080907@am.sony.com> (raw)
In-Reply-To: <20120229181430.GI3318@game.jcrosoft.org>
On 02/29/2012 10:14 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 08:58 Wed 29 Feb , Stephen Warren wrote:
>> Jean-Christophe PLAGNIOL-VILLARD wrote at Wednesday, February 29, 2012 5:30 AM:
>>> On 17:03 Tue 28 Feb , Stephen Warren wrote:
>>>> uImage files typically encode a single absolute load and entry address.
>>>> This is inconvenient when attempting to share that uImage across multiple
>>>> SoCs with different physical RAM addresses. Recent versions of mkimage
>>>> implement a "kernel_noload" image type which encodes no absolute load
>>>> address, and a relative entry address. This works well for uImage-wrapped
>>>> ARM zImages, since they are relocatable.
>>>>
>>>> This is enabled by commit b9b50e89d317c58becd0e2d7fac2e21e3a81dd0a
>>>> "image: Implement IH_TYPE_KERNEL_NOLOAD" in U-Boot.
>>>>
>>>> Signed-off-by: Stephen Warren <swarren@nvidia•com>
>>>> ---
>>>> I assume I should put this into the ARM patch tracker if it's OK?
>>>
>>> Again a new option for uImage no why not just boot the zImage
>>>
>>> in this case the uImage is useless
>>
>> U-Boot doesn't support zImage at present.
>>
>> A patch was posted to support it at least for ARM, but needed a little
>> work before it could be committed.
> Sorry I see no advantage to have the uImage build by the kernel anymore as
> we have a relocatable zImage
>
> I'll even drop its support
This seems at least premature, and possibly ill-advised in general.
There are lots of U-Boot images out in the field, many of which that
are rarely updated. A lot of workflow will be disrupted unnecessarily
by a change like this.
Could you wait to drop uImage build support in the kernel until
U-Boot supports zImage, and has worked it's way into the field
for a few years?
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================
next prev parent reply other threads:[~2012-02-29 18:33 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 [this message]
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
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=4F4E6F96.8080907@am.sony.com \
--to=tim.bird@am$(echo .)sony.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