From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Thu, 10 Nov 2011 09:04:28 -0700 Subject: [U-Boot] [PATCH 1/2] image: Implement IH_TYPE_KERNEL_ANYLOAD In-Reply-To: <201111101058.04524.marek.vasut@gmail.com> References: <1320860840-6347-1-git-send-email-swarren@nvidia.com> <201111101058.04524.marek.vasut@gmail.com> Message-ID: <4EBBF60C.3000906@nvidia.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 11/10/2011 02:58 AM, Marek Vasut wrote: >> The legacy uImage format includes an absolute load and entry-point >> address. When bootm operates on a kernel uImage in memory that isn't >> loaded at the address in the image's load address, U-Boot will copy >> the image to its address in the header. >> >> Some kernel images can actually be loaded and used at any arbitrary >> address. An example is an ARM Linux kernel zImage file. To represent >> this capability, IH_TYPE_KERNEL_ANYLOAD is implemented, which operates >> just like IH_TYPE_KERNEL, except that the load address header is >> ignored, and U-Boot does not copy the image to its load address, but >> rather uses it in-place. >> >> This is useful when sharing a single (uImage-wrapped) zImage across >> multiple boards with different memory layouts; in this case, a specific >> load address need not be picked when creating the uImage, but instead >> is selected by the board-specific U-Boot environment used to load and >> boot that image. >> >> Signed-off-by: Stephen Warren >> --- > > Hi Stephen, > > just a silly question, but didn't we agree on cmd_bootz? Or is this unrelated ? bootz did seem to be agreed upon initially, but Wolfgang's most recent response suggested that a new IH_TYPE would be acceptable, and it's a lot less code to implement. At a later point, bootz could still be implemented if desired. -- nvpublic