From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uboot-tools: fix dtc invocation
Date: Fri, 1 Dec 2017 09:52:57 +0100 [thread overview]
Message-ID: <20171201095257.0db57c88@windsurf.lan> (raw)
In-Reply-To: <20171201073027.23072-1-yegorslists@googlemail.com>
Hello,
On Fri, 1 Dec 2017 08:30:27 +0100, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> In Buildroot we don't perform Kconfig configuration for
> u-boot-tools, hence CONFIG_MKIMAGE_DTC_PATH is empty.
Should we do a Kconfig configuration ?
Or alternatively, can we pass CONFIG_MKIMAGE_DTC_PATH=dtc on the build
command line ?
Also: is this broken in master ? In next ? What is this fixing ? (Note:
I know all of this because we discussed it on IRC, but it should be in
the commit log).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-01 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 7:30 [Buildroot] [PATCH] uboot-tools: fix dtc invocation yegorslists at googlemail.com
2017-12-01 8:52 ` Thomas Petazzoni [this message]
2017-12-01 9:44 ` Yegor Yefremov
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=20171201095257.0db57c88@windsurf.lan \
--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