[Buildroot] uboot-tools and uboot being separate

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Wed Feb 13 23:14:04 UTC 2013

Dear Arnout Vandecappelle,

On Wed, 13 Feb 2013 23:57:03 +0100, Arnout Vandecappelle wrote:

>   I've had the same issue once: a patch to add some functionality to 
> mkimage that I needed both on the host and on the target.

Then easy enough; put your patch in package/uboot-tools/. It handles
the build and installation of both the host *and* target variant of the
U-Boot tools.

> > No. You don't have to have identical uboot-tools and uboot.
> > Basically uboot-tools provide one tool to create U-Boot images
> > (mkimage) and tools to manipulate the U-Boot environment from Linux
> > (fw_printenv, fw_setenv). Those tools are backward compatible, and
> > so you can perfectly use the tools from U-Boot 2010.x with a
> > running U-Boot 2012.x or 2013.x.
>   Unless some feature has been added or removed.

In which case you bump the version of the uboot-tools package, just
like any other package.

Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.

More information about the buildroot mailing list