From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933439Ab1JNURy (ORCPT ); Fri, 14 Oct 2011 16:17:54 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:57904 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933330Ab1JNURw (ORCPT ); Fri, 14 Oct 2011 16:17:52 -0400 Date: Fri, 14 Oct 2011 21:17:37 +0100 From: Russell King - ARM Linux To: Nicolas Pitre Cc: Arnd Bergmann , Stephen Warren , Olof Johansson , Peter De Schrijver , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-tegra@vger.kernel.org" , "Colin Cross (ccross@android.com)" , Erik Gilling Subject: Re: [PATCH] arm/tegra: select AUTO_ZRELADDR by default Message-ID: <20111014201737.GW21648@n2100.arm.linux.org.uk> References: <1317172068-14872-1-git-send-email-pdeschrijver@nvidia.com> <201110141729.41515.arnd@arndb.de> <74CDBE0F657A3D45AFBB94109FB122FF173BE1A283@HQMAIL01.nvidia.com> <201110141827.53906.arnd@arndb.de> <20111014192057.GT21648@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 14, 2011 at 04:14:12PM -0400, Nicolas Pitre wrote: > On Fri, 14 Oct 2011, Russell King - ARM Linux wrote: > > > On Fri, Oct 14, 2011 at 02:01:07PM -0400, Nicolas Pitre wrote: > > > The way I'm restructuring things around this is that AUTO_ZRELADDR will > > > always be active by default, just like ARM_PATCH_PHYS_VIRT now. This > > > platform specific exclusion thinking is a step backward so I'd prefer if > > > people would refrain from going there for the moment. > > > > Are you expecting everyone to change the way they load the zImage > > overnight then? > > No, of course. But adding restrictions in the kernel build because > u-Boot's own image format dictates such restrictions doesn't make sense. > Those restrictions must be pushed towards the uImage encapsulation step, > not higher the kernel config hierarchy. You're not understanding again. I'm talking about people who _explicitly_ load the zImage at a different address to which the decompressed image ends up. With AUTO_ZRELADDR=y their setup will break unless they stop that behaviour, which takes away one of the advantages of using the zImage format.