u-boot.git/Makefile, branch v2016.03-rc1

Prepare v2016.03-rc1

2016-02-02T16:29:50+00:00

Signed-off-by: Tom Rini

Makefile: Drop unnecessary -dtb suffixes

2016-02-02T01:55:52+00:00

When OF_CONTROL is enabled, u-boot-dtb.* files are the same as u-boot.*
files. So we can use the latter for simplicity.

Tested-by: Stephen Warren 
Signed-off-by: Simon Glass

Makefile: Make u-boot.img the same as u-boot-dtb.img

2016-02-02T01:55:50+00:00

Create u-boot.img even when OF_CONTROL is enabled, so that this file can be
used in both cases.

Tested-by: Stephen Warren 
Signed-off-by: Simon Glass

socfpga: Simplify Makefile filenames

2016-02-02T01:55:48+00:00

We don't need the -dtb suffix anymore, so drop it.

Tested-by: Stephen Warren 
Signed-off-by: Simon Glass

tegra: Always build a boot image with the same filename

2016-02-02T01:55:43+00:00

Adjust the Makefile to build u-boot-tegra.bin which contains a device tree
if OF_SEPARATE is enabled, and does not if not. This mirrors U-Boot's new
approach of using u-boot.bin to handle both cases.

Tested-by: Stephen Warren 
Signed-off-by: Simon Glass

fdt: Build a U-Boot binary without device tree

2016-02-02T01:55:32+00:00

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 
Reviewed-by: Stephen Warren 
Signed-off-by: Simon Glass

tegra: Clarify generation of -nodtb file with OF_CONTROL

2016-02-02T01:55:13+00:00

Fix the ALL-y logic in the Makefile so that is clear that we always want
the -nodtb file.

Tested-by: Stephen Warren 
Reviewed-by: Stephen Warren 
Signed-off-by: Simon Glass

Move all command code into its own directory

2016-01-25T15:39:43+00:00

There are a lot of unrelated files in common, including all of the commands.
Moving them into their own directory makes them easier to find and is more
logical.

Some commands include non-command code, such as cmd_scsi.c. This should be
sorted out at some point so that the function can be enabled with or without
the associated command.

Unfortunately, with m68k I get this error:

m68k:  +   M5329AFEE
+arch/m68k/cpu/mcf532x/start.o: In function `_start':
+arch/m68k/cpu/mcf532x/start.S:159:(.text+0x452): relocation truncated to fit: R_68K_PC16 against symbol `board_init_f' defined in .text.board_init_f section in common/built-in.o

I hope someone can shed some light on what this means. I hope it isn't
depending on the position of code in the image.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng 
Reviewed-by: Heiko Schocher 
Acked-by: Stefan Roese 
Acked-by: Przemyslaw Marczak

kbuild: drop workaround for old style CONFIG_SYS_TEXT_BASE defines

2016-01-20T15:19:37+00:00

Now, there is no board defining CONFIG_SYS_TEXT_BASE by its config.mk,
so this workaround is no longer needed.

Signed-off-by: Masahiro Yamada 
Acked-by: Stefan Roese

arm: mvebu: Add runtime detection of UART (xmodem) boot-mode

2016-01-14T13:08:59+00:00

This patch adds runtime detection of the Marvell UART boot-mode (xmodem
protocol). If this boot-mode is detected, SPL will return to the
BootROM to continue the UART booting.

With this patch its now possible, to generate a U-Boot image that
can be booted either from the strapped boot-device (e.g. SPI NOR, MMC,
etc) or via the xmodem protocol from the UART. In the UART case,
the kwboot tool will dynamically insert the UART boot-device type
into the image. And also patch the load address in the header, so
that the mkimage header will be skipped (as its not expected by the
Marvell BootROM).

This simplifies the development for Armada XP / 38x based boards.
As no special images need to be generated by selecting the
MVEBU_BOOTROM_UARTBOOT Kconfig option.

Since the Kconfig option MVEBU_BOOTROM_UARTBOOT is not needed any
more, its now completely removed.

Signed-off-by: Stefan Roese 
Cc: Luka Perkov 
Cc: Dirk Eibach 
Cc: Phil Sutter 
Cc: Kevin Smith