From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] uboot-tools and uboot being separate
Date: Thu, 14 Feb 2013 00:21:12 +0100 [thread overview]
Message-ID: <511C1FE8.60103@mind.be> (raw)
In-Reply-To: <20130214001404.199dbd64@skate>
On 14/02/13 00:14, Thomas Petazzoni wrote:
> 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.
In my particular use case (IIRC), the patched mkimage was used to
process u-boot.bin into a ROM-bootable image. So the same patch had to be
applied to uboot-tools and uboot. But it was not in fact the same patch,
because the uboot version was different. What we did in the end is just
change the uboot-tools site to the same git repository.
>>> 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.
Yes, but you have to do it twice.
It's not that it's impossible to solve, it's just inconvenient and
counter-intuitive. It's also inconvenient to have two U-Boot versions in
your legal-info output. Just like it's inconvenient to have two linux
tarballs.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-02-13 23:21 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
2013-02-13 23:21 ` Arnout Vandecappelle [this message]
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=511C1FE8.60103@mind.be \
--to=arnout@mind.be \
--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