From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aneesh V <aneesh@ti.com>
Date: Wed, 18 May 2011 10:32:34 +0530
Subject: [U-Boot] [PATCH v2 18/22] armv7: embed u-boot size within
 u-boot for use from SPL
In-Reply-To: <20110515200939.16E5F1491B06@gemini.denx.de>
References: <1298893591-17636-1-git-send-email-aneesh@ti.com>
	<1305472900-4004-19-git-send-email-aneesh@ti.com>
	<20110515200939.16E5F1491B06@gemini.denx.de>
Message-ID: <4DD352EA.3090007@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 Wolfgang,

On Monday 16 May 2011 01:39 AM, Wolfgang Denk wrote:
> Dear Aneesh V,
>
> In message<1305472900-4004-19-git-send-email-aneesh@ti.com>  you wrote:
>> Embed the u-boot flash image size at a known offset from the
>> start of u-boot so that SPL can use it while loading u-boot
>> from a non-XIP media.
>
> I don't think this is a good idea.
>
> What you are doing here is defining an image format. Such an image
> format must be good enough not only for OMAP4 and for loading U-Boot
> as second stage, but for all other architectures and use cases as
> well.

I am not defining and publishing a format for the external world. It's
just an internal information much like any other info embedded in
start.S such as  _bss_end_ofs, _end_ofs etc. It's just that SPL, being
an insider, can take advantage of it.

I feel creating a new mkimage target just for this will be an overkill.
I will be happy loading the maximum image size always.

best regards,
Aneesh