From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bartlomiej Sieka <tur@semihalf.com>
Date: Wed, 26 Mar 2008 17:31:40 +0100
Subject: [U-Boot-Users] RFC: make new image support mandatory
In-Reply-To: <20080326164102.58905a27@hskinnemo-gx620.norway.atmel.com>
References: <20080326141644.D180D243A7@gemini.denx.de>
	<20080326164102.58905a27@hskinnemo-gx620.norway.atmel.com>
Message-ID: <47EA7A6C.3050301@semihalf.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

Haavard Skinnemoen wrote:
> On Wed, 26 Mar 2008 15:16:44 +0100
> Wolfgang Denk <wd@denx.de> wrote:
> 
>> now that the new image  format  has  been  merged  into  mainline,  I
>> propose  that  we  make it mandatory for all newly added boards. That
>> means, that each new board that gets added shall at least contain
>>
>> 	#define CONFIG_FIT              1
>>
>> in it's board config file; I recommend to add also
>>
>> 	#define CONFIG_FIT_VERBOSE      1 /* enable fit_format_{error,warning}() */
>>
>>
>> Can we agree on this?
> 
> Oh my...
> 
> Configuring for atstk1002 board...
>    text	   data	    bss	    dec	    hex	filename
>  112936	   8032	 216860	 337828	  527a4	./u-boot
> 
> with CONFIG_FIT and CONFIG_OF_LIBFDT enabled, compared to
> 
>    text	   data	    bss	    dec	    hex	filename
>   87724	   6840	 215848	 310412	  4bc8c	./u-boot

BTW: were you able to compile the tools/ directory for the above board?
If yes, what were the differences versus the failing build you posted in
your other email?

> 
> on v1.3.2. That's 26KB...do we really want to make something _that_
> expensive mandatory? Or can I somehow disable the old code to reclaim
> some of it?

There's no easy way to disable support for the old format currently.

Regards,
Bartlomiej