All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Sieka <tur@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: make new image support mandatory
Date: Wed, 26 Mar 2008 17:31:40 +0100	[thread overview]
Message-ID: <47EA7A6C.3050301@semihalf.com> (raw)
In-Reply-To: <20080326164102.58905a27@hskinnemo-gx620.norway.atmel.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

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

  reply	other threads:[~2008-03-26 16:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 14:16 [U-Boot-Users] RFC: make new image support mandatory Wolfgang Denk
2008-03-26 14:26 ` Kumar Gala
2008-03-26 14:54   ` Bartlomiej Sieka
2008-03-26 14:57   ` Wolfgang Denk
2008-03-26 15:24     ` Kumar Gala
2008-03-26 14:52 ` Bartlomiej Sieka
2008-03-26 15:28 ` Haavard Skinnemoen
2008-03-26 16:24   ` Bartlomiej Sieka
2008-03-27  1:24     ` Jerry Van Baren
2008-03-27  7:04       ` Stefan Roese
2008-03-27  7:19         ` Liu Dave
2008-03-27  8:16           ` Wolfgang Denk
2008-03-27  8:55         ` Dave Liu
2008-03-26 15:41 ` Haavard Skinnemoen
2008-03-26 16:31   ` Bartlomiej Sieka [this message]
2008-03-27  8:12     ` Haavard Skinnemoen
2008-03-27  9:01       ` Stefan Roese
2008-03-27  9:06         ` Roy Zang
2008-03-27 10:15         ` Markus Klotzbücher
2008-03-27  9:09       ` Dave Liu
2008-03-27 13:52       ` Bartlomiej Sieka
2008-04-01  9:26     ` Luigi 'Comio' Mantellini
2008-04-01  9:40       ` Bartlomiej Sieka
2008-03-26 20:37   ` Guennadi Liakhovetski
2008-03-26 22:10     ` Wolfgang Denk
2008-03-27  1:24     ` Shinya Kuribayashi
2008-03-27  1:43   ` Jerry Van Baren
2008-03-27  9:59 ` Jean-Christophe PLAGNIOL-VILLARD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47EA7A6C.3050301@semihalf.com \
    --to=tur@semihalf.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.