summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2016-01-31 18:10:50 -0700
committerTom Rini <trini@konsulko.com>2016-02-01 20:55:32 -0500
commitad1ecd2063dae55ccfca994a7c9fdec2462b18ab (patch)
tree87bfe60aa6a9d62271e367b0b971f7e01d1f718e /scripts
parent580cc033124f17d20d5bc362984c36ba441f99e7 (diff)
downloadblackbird-obmc-uboot-ad1ecd2063dae55ccfca994a7c9fdec2462b18ab.tar.gz
blackbird-obmc-uboot-ad1ecd2063dae55ccfca994a7c9fdec2462b18ab.zip
fdt: Build a U-Boot binary without device tree
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. Adjust 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 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. Adjust tegra rules so it continues to produce the correct files. Tested-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud