From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] uboot-tools and uboot being separate
Date: Thu, 14 Feb 2013 00:14:04 +0100 [thread overview]
Message-ID: <20130214001404.199dbd64@skate> (raw)
In-Reply-To: <511C1A3F.2080804@mind.be>
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
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-13 23:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 17:22 [Buildroot] uboot-tools and uboot being separate Dimitrios Siganos
2013-02-13 20:20 ` Thomas Petazzoni
2013-02-13 22:57 ` Arnout Vandecappelle
2013-02-13 23:14 ` Thomas Petazzoni [this message]
2013-02-13 23:21 ` Arnout Vandecappelle
2013-02-14 2:15 ` Dimitrios Siganos
2013-02-14 7:57 ` Thomas Petazzoni
2013-02-14 16:18 ` Dimitrios Siganos
2013-02-14 0:09 ` Dimitrios Siganos
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=20130214001404.199dbd64@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox