From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Thu, 22 Dec 2011 05:04:01 +0100 Subject: [U-Boot] Building uImage with multiple load addresses In-Reply-To: <4EF2792A.5060800@nvidia.com> References: <4EF2792A.5060800@nvidia.com> Message-ID: <201112220504.01444.marek.vasut@gmail.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 12/21/2011 03:20 PM, Fabio Estevam wrote: > > On Wed, Dec 21, 2011 at 7:24 PM, Fabio Estevam wrote: > >> Hi, > >> > >> When trying to build imx_v4_v5_defconfig, or mx3_defconfig, or > >> mx5_defconfig on a 3.2-rc6 kernel I get: > >> ... > >> multiple load addresses: 0x80008000 0x80008000 0x10008000 > >> This is incompatible with uImages > >> ... > >> Do I need to do any changes to mkimage? > >> ... > > I'd suggest using "mkimage -t kernel_noload" instead of "mkimage -t > kernel". That way, you don't have to specify an load/entry address; the > kernel will be executed wherever you happen to load it in memory, which > should work fine for an ARM zImage at least. > > This feature was introduced pretty recently in mainline U-Boot though, > so you'll need to build your own new U-boot and mkimage tool. I think this is fine. And I agree to use this approach. Stephen, I won't be able to finish the u-boot/zImage support any soon, exams started for me now. M