From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean-Christophe PLAGNIOL-VILLARD Subject: Re: [PATCH 1/2] ARM: Add Kconfig option to use mkimage -T kernel_noload Date: Wed, 29 Feb 2012 13:29:42 +0100 Message-ID: <20120229122942.GF3318@game.jcrosoft.org> References: <1330473804-23348-1-git-send-email-swarren@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1330473804-23348-1-git-send-email-swarren@nvidia.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Stephen Warren Cc: Russell King , Nicolas Pitre , Peter De Schrijver , linux-tegra@vger.kernel.org, Colin Cross , Olof Johansson , linux-arm-kernel@lists.infradead.org List-Id: linux-tegra@vger.kernel.org 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 > --- > 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 Best Regards, J.