[U-Boot-Users] RFC: make new image support mandatory

[Jerry Van Baren <gvb.uboot@gmail.com>]

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
> 
> 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?
> 
> Haavard

On a PowerPC target that includes libfdt already...

Configuring for MPC8360EMDS board with CONFIG_FIT:

    text	   data	    bss	    dec	    hex	filename
  231588	  12072	  26836	 270496	  420a0	./u-boot

without CONFIG_FIT:

    text	   data	    bss	    dec	    hex	filename
  211648	  11604	  26796	 250048	  3d0c0	./u-boot

delta text = 19940 (19.5K).  Still pretty heavy.  :-/  I have not looked 
at where the weight is coming from, just thought it would be interesting 
to see what the delta looked like when libfdt was already included.  I 
was expecting a bigger hit from libfdt and less from FIT.  Hmmmm.

Best regards,
gvb