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 v3 0/7] fdt: Replace u-boot-dtb.bin with u-boot.bin
Date: Mon, 1 Feb 2016 16:00:30 -0700	[thread overview]
Message-ID: <56AFE38E.1060502@wwwdotorg.org> (raw)
In-Reply-To: <1454289055-17054-1-git-send-email-sjg@chromium.org>

On 01/31/2016 06:10 PM, Simon Glass wrote:
> At present u-boot.bin holds the plain U-Boot binary without the device tree.
> This is somewhat annoying since you need either u-boot.bin or u-boot-dtb.bin
> depending on whether device tree is used.
>
> This series adjusts the build such that u-boot.bin includes a device tree if
> enabled, and the plain binary is in u-boot-nodtb.bin. For now u-boot-dtb.bin
> remains the same.
>
> This should be acceptable since:
>
> - without OF_CONTROL, u-boot.bin still does not include a device tree
> - with OF_CONTROL, u-boot-dtb.bin does not change
>
> The main impact is to build systems which are set up to use u-boot.bin as
> the output file and then add a device tree. These will have to change to use
> u-boot-nodtb.bin instead.
>
> The original decision to use a separate u-boot-dtb.bin was aimed at allowing
> any device tree file to be concatenated to the u-boot.bin image after the
> build. However this no-longer seems so important. More important is the
> convenience of using the same output file regardless of the setting for
> OF_CONTROL.

The series,
Tested-by: Stephen Warren <swarren at nvidia.com

(Both out T124-and-before and T210-and-later flashing processes still 
seem to work OK with the new file naming etc.)

Patches 1-3,
Reviewed-by: Stephen Warren <swarren@nvidia.com>

  parent reply	other threads:[~2016-02-01 23:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01  1:10 [U-Boot] [PATCH v3 0/7] fdt: Replace u-boot-dtb.bin with u-boot.bin Simon Glass
2016-02-01  1:10 ` [U-Boot] [PATCH v3 1/7] tegra: Clarify generation of -nodtb file with OF_CONTROL Simon Glass
2016-02-02  1:57   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-02-02  1:58   ` Tom Rini
2016-02-01  1:10 ` [U-Boot] [PATCH v3 2/7] fdt: Build a U-Boot binary without device tree Simon Glass
2016-02-02  1:58   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-02-01  1:10 ` [U-Boot] [PATCH v3 3/7] fdt: Build an SPL " Simon Glass
2016-02-02  1:58   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-02-01  1:10 ` [U-Boot] [PATCH v3 4/7] tegra: Always build a boot image with the same filename Simon Glass
2016-02-01 22:52   ` Stephen Warren
2016-02-02  1:58   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-02-01  1:10 ` [U-Boot] [PATCH v3 5/7] socfpga: Simplify Makefile filenames Simon Glass
2016-02-02  1:58   ` [U-Boot] [U-Boot,v3,5/7] " Tom Rini
2016-02-01  1:10 ` [U-Boot] [PATCH v3 6/7] Makefile: Make u-boot.img the same as u-boot-dtb.img Simon Glass
2016-02-01 22:54   ` Stephen Warren
2016-02-02  1:59     ` Tom Rini
2016-02-02  1:58   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-02-01  1:10 ` [U-Boot] [PATCH v3 7/7] Makefile: Drop unnecessary -dtb suffixes Simon Glass
2016-02-02  1:58   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-02-01  7:31 ` [U-Boot] [PATCH v3 0/7] fdt: Replace u-boot-dtb.bin with u-boot.bin Albert ARIBAUD
2016-02-02  0:05   ` Simon Glass
2016-02-01 23:00 ` Stephen Warren [this message]
2016-02-02  1:59   ` Tom Rini

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=56AFE38E.1060502@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