From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 11 Mar 2008 11:37:05 +1100 From: David Gibson To: Kumar Gala Subject: Re: [PATCH] [POWERPC] bootwrapper: Allow specifying of image physical offset Message-ID: <20080311003705.GH11559@localhost.localdomain> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: linuxppc-dev@ozlabs.org, Paul Mackerras List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Mar 07, 2008 at 10:55:51AM -0600, Kumar Gala wrote: > Normally we assume kernel images will be loaded at offset 0. However > there are situations, like when the kernel itself is running at a non-zero > physical address, that we don't want to load it at 0. > > Allow the wrapper to take an offset. We use this when building u-boot images. > > Signed-off-by: Kumar Gala Hrm. It concerns me that with the patch as it stands, CONFIG_MEMORY_START looks like a fairly universal option, but it will only be respected on u-boot platforms (and only new u-boot, not cuboot at that). -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson