From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aneesh V <aneesh@ti.com>
Date: Fri, 04 Nov 2011 07:41:45 +0530
Subject: [U-Boot] SPL support and secondary image size
In-Reply-To: <4EB31D2A.3070107@freescale.com>
References: <CAKON4OwDvSWqyme5HagzTQ8Y5zj5rorFB04B5Mmwet2ErObPfg@mail.gmail.com>
	<4EB31D2A.3070107@freescale.com>
Message-ID: <4EB349E1.7010907@ti.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Jon,

On Friday 04 November 2011 04:30 AM, Scott Wood wrote:
> On 11/03/2011 05:20 PM, jonsmirl at gmail.com wrote:

Looks like I am not seeing some mails in this thread. I didn't get your
first mail, neither Tom Rini's mails.

>> My primary SPL image needs the size of the secondary image built into
>> it. How do I access that size while building the primary SPL image?

For OMAP we find this run-time by loading u-boot.img instead of
u-boot.bin. u-boot.img has a 64 byte header with all necessary
information such as size, load address, image type etc. The OMAP SPL
can in fact load any image that has a standard u-boot header(mkimage
header), including a uImage. This scheme was suggested by Wolfgang.

>
> Does it need to be exact?  Usually we just hardcode something that
> should be big enough.
>
> -Scott
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot