[U-Boot] [PATCH 0/6] Adjust command macros to allow smaller U-Boot size

Tom Rini trini at ti.com
Mon Mar 31 20:59:58 CEST 2014


On Mon, Mar 31, 2014 at 12:38:20PM -0600, Simon Glass wrote:
> Hi Tom,
> 
> On 31 March 2014 12:30, Tom Rini <trini at ti.com> wrote:
> 
> > On Mon, Mar 24, 2014 at 09:51:05AM -0600, Simon Glass wrote:
> >
> > > A large chunk of U-Boot's executable size is the code to process and
> > > execute commands. This is reasonable, since commands and scripts are
> > > an important part of U-Boot's feature set and provide much of its
> > > flexibility.
> > >
> > > However, for some applications only a very limited set of commands is
> > > required. Where image size is important, it is desirable to be able to
> > > easily remove unwanted code.
> > >
> > > This series introduces a new board_run_command() function which can
> > > be used to run a small subset of commands as required by the board
> > > (typically load and bootm), thus allowing the rest of the commands
> > > to be automatically and reliably dropped from the image using toolchain
> > > dead code elimination.
> >
> > This is an interesting concept certainly.  Can you also provide a
> > non-trivial example here?
> >
> 
> I have a very non-trivial example which is a lot of code, and calls things
> like the SPI layer and do_bootm(). That might be more than you want.
> 
> Would it help if I wrote a simple FDT-based boot to a kernel in a function?

How about both?

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140331/7b3d8486/attachment.pgp>


More information about the U-Boot mailing list