public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tegra: allow build to succeed with SPL disabled
Date: Thu, 31 Oct 2013 10:29:13 -0600	[thread overview]
Message-ID: <52728559.2010409@wwwdotorg.org> (raw)
In-Reply-To: <1383211298-31071-1-git-send-email-vidyas@nvidia.com>

On 10/31/2013 03:21 AM, Vidya Sagar wrote:
> u-boot-dtb-tegra.bin and u-boot-nodtb-tegra.bin binaries
> are generated only if the SPL build is enabled as they have
> dependency on SPL build

Should they though? If there's no SPL, surely we still want to generate
the same output filenames, so that consumers of the binaries don't have
to care whether a particular board needs the SPL tacked onto the binary.

In other words, rather than:

u-boot-nodtb-tegra.bin == SPL + U-Boot
u-boot-dtb-tegra.bin == SPL + U-Boot + DTB

... when SPL is disabled, shouldn't we generate:

u-boot-nodtb-tegra.bin == U-Boot
u-boot-dtb-tegra.bin == U-Boot + DTB

That would require modifying the rules that generate those files not to
include the SPL binary in the concatenation, rather than simply not
generating those files at all.

  parent reply	other threads:[~2013-10-31 16:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31  9:21 [U-Boot] [PATCH] tegra: allow build to succeed with SPL disabled Vidya Sagar
2013-10-31 16:08 ` Tom Warren
     [not found]   ` <113ACA888B71994BB56E5CF3704953486D6631A701@BGMAIL02.nvidia.com>
2013-11-01 13:24     ` Vidya Sagar
2013-11-01 13:28     ` Vidya Sagar
2013-11-01 17:27   ` Vidya Sagar
2013-11-01 17:34     ` Stephen Warren
2013-11-01 17:41       ` Vidya Sagar
2013-10-31 16:29 ` Stephen Warren [this message]
2013-11-01 17:29   ` Vidya Sagar
2013-11-01 17:39     ` Stephen Warren

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=52728559.2010409@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /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