From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using u-boot tools
Date: Mon, 29 Sep 2014 15:21:36 +0200 [thread overview]
Message-ID: <20140929152136.4d7cee9c@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LXTaWD=4KrL3oF3Sy4dP+cFbX5fBK3LD7WACtRvuhxmqw@mail.gmail.com>
Dear Thomas De Schampheleire,
On Mon, 29 Sep 2014 11:32:52 +0200, Thomas De Schampheleire wrote:
> >> I am using customized uboot-tools 2010.03 and want to retain that. In 2014,
> >> the tools selection is new, but I want to use the source code for
> >> uboot-tools used in 2010.03, as this is having some changes. I want to get
> >> the "fw_printenv" compiled with a "-D" flag.
> >>
> >> Can anyone please help me in this regard?
> >
> > Well, just add a patch in package/uboot-tools/ to make whatever change
> > you want to the U-Boot source code used for your U-Boot tools.
>
> As this change will not be upstreamable to buildroot, I would rather
> recommend to use BR2_GLOBAL_PATCH_DIR, to not pollute the upstream
> buildroot sources. See http://nightly.buildroot.org/#customize-patches
Absolutely, that's a good point. Thanks for reminding me about this!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-29 13:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 7:38 [Buildroot] Using u-boot tools Kantanu Kumar Mohapatra
2014-09-29 9:18 ` Thomas Petazzoni
2014-09-29 9:32 ` Thomas De Schampheleire
2014-09-29 13:21 ` Thomas Petazzoni [this message]
2014-09-29 15:59 ` Kantanu Kumar Mohapatra
2014-09-29 16:38 ` Thomas Petazzoni
2014-09-29 18:43 ` Kantanu Kumar Mohapatra
2014-09-29 19:14 ` Thomas De Schampheleire
2014-09-29 19:41 ` Kantanu Kumar Mohapatra
2014-09-29 19:58 ` Thomas De Schampheleire
2014-09-30 9:33 ` Kantanu Kumar Mohapatra
2014-09-30 9:58 ` Thomas De Schampheleire
2014-09-30 13:16 ` Kantanu Kumar Mohapatra
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=20140929152136.4d7cee9c@free-electrons.com \
--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