From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] boot/uboot: add missing SPL build dependency
Date: Fri, 2 Sep 2016 14:41:17 +0200 [thread overview]
Message-ID: <20160902144117.12287cbd@free-electrons.com> (raw)
In-Reply-To: <9e8b258d-39e7-1cd4-7530-e295ee7e09b6@mind.be>
Hello,
On Fri, 2 Sep 2016 09:13:07 +0200, Arnout Vandecappelle wrote:
> Note BTW that the current situation is already broken for OMAP3 when using a
> recent U-Boot. We only call the 'u-boot.img' target, and this _doesn't_ build
> MLO. We should also 'make all'. I guess we don't do 'make all' to avoid doing
> redundant work when SPL isn't required, but it's kind of useless :-)
Is there a reason to not do "make all" ?
There might some image formats that are *not* produced by default (I'm
thinking things like .kwb images). But maybe we need to use "make all"
by default, and only in specific case use a special target.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-02 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 14:51 [Buildroot] boot/uboot: allow multiple target selection Petr Kulhavy
2016-09-01 14:51 ` [Buildroot] [PATCH 1/2] boot/uboot: add missing SPL build dependency Petr Kulhavy
2016-09-02 7:13 ` Arnout Vandecappelle
2016-09-02 12:41 ` Thomas Petazzoni [this message]
2016-09-03 15:11 ` Petr Kulhavy
2016-09-17 17:35 ` Thomas Petazzoni
2016-09-01 14:51 ` [Buildroot] [PATCH 2/2] boot/uboot: allow to build multiple Uboot images Petr Kulhavy
2016-09-02 7:13 ` Arnout Vandecappelle
2016-09-02 10:53 ` Petr Kulhavy
2016-09-02 18:50 ` Arnout Vandecappelle
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=20160902144117.12287cbd@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