buildroot/boot, branch 2016.11

uboot: support -b option for mkenvimage

2016-11-30T15:10:30+00:00

When generating the environment image the target endianess should be taken in account for CRC calculation purposes. For big endian targets the -b flag should be passed to the mkenvimage tool. Signed-off-by: Tiago Brusamarello Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

boot-wrapper-aarch64: update upstream repository

2016-11-16T11:24:19+00:00

cmarinas/boot-wrapper-aarch64.git does not exist any more. Switch over to mark/boot-wrapper-aarch64.git. Signed-off-by: Masahiro Yamada Cc: Catalin Marinas Cc: Mark Rutland Signed-off-by: Thomas Petazzoni

package/uboot: define help commands when using Kconfig

2016-11-01T13:51:15+00:00

Expose the Kconfig-related help commands when U-Boot uses the Kconfig configuration. Like others (like Linux, barebox, busybox), only expose menuconfig, not all the configurators. Signed-off-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

boot-wrapper-aarch64: Allow users to select the PSCI SMP boot method

2016-10-25T21:59:36+00:00

Signed-off-by: Hollis Blanchard [Thomas: - remove "default n" - pass explicit --disable-psci] Signed-off-by: Thomas Petazzoni

uboot: add option to optionally depend on host-openssl

2016-10-20T21:31:09+00:00

Some U-Boot board configurations have CONFIG_FIT_SIGNATURE=y. In this case, when U-Boot builds its tools, it requires OpenSSL support on the host system. Since we clearly don't want to unconditionally depend on host-openssl, we introduce a new option to explicitly enable the dependency on host-openssl. This is exactly identical to the existing BR2_TARGET_UBOOT_NEEDS_DTC, for the dependency on host-dtc. It is therefore the responsibility of the user to enable this option if his board configuration uses CONFIG_FIT_SIGNATURE=y. Necessary to fix bug #9316. Signed-off-by: Thomas Petazzoni

core: introduce per br2-external NAME

2016-10-16T11:01:02+00:00

This unique NAME is used to construct a per br2-external tree variable, BR2_EXTERNAL_$(NAME)_PATH, which contains the path to the br2-external tree. This variable is available both from Kconfig (set in the Kconfig snippet) and from the .mk files. Also, display the NAME and its path as a comment in the menuconfig. This will ultimately allow us to support multiple br2-external trees at once, with that NAME (and thus BR2_EXTERNAL_$(NAME)) uniquely defining which br2-external tree is being used. The obvious outcome is that BR2_EXTERNAL should now no longer be used to refer to the files in the br2-external tree; that location is now known from the BR2_EXTERNAL_$(NAME)_PATH variable instead. This means we no longer need to expose, and must stop from from exposing BR2_EXTERNAL as a Kconfig variable. Finally, this also fixes a latent bug in the pkg-generic infra, where we would so far always refer to BR2_EXTERNAL (even if not set) to filter the names of packages (to decide whether they are a bootloader, a toolchain or a simple package). Note: since the variables in the Makefile and in Kconfig are named the same, the one we computed early on in the Makefile will be overridden by the one in .config when we have it. Thus, even though they are set to the same raw value, the one from .config is quoted and, being included later in the Makefile, will take precedence, so we just re-include the generated Makefile fragment a third time before includeing the br2-external's Makefiles. That's unfortunate, but there is no easy way around that as we do want the two variables to be named the same in Makefile and Kconfig (and we can't ask the user to un-quote that variable himself either), hence this little dirty triple-inclusion trick. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Arnout Vandecappelle Cc: Romain Naour Signed-off-by: Peter Korsgaard

arm-trusted-firmware: new package

2016-10-15T12:13:34+00:00

Signed-off-by: Joao Pinto [Thomas: - Rename the package from atfirmware to arm-trusted-firmware, in order to match upstream. - Remove option to apply custom patches. We no longer add such options, and use the global patch directory instead. - Rename the repo URL/version options, in order to not be Git specific, in case support for fetching from other VCS is added later. This is consistent with how other bootloaders handle this. - Add license information. - Do not add a weird dependency on the vexpress-firmware package in Config.in. Instead, simply use it if it's available. Of course, some configurations (such as the juno configuration) will fail to build if vexpress-image is not enabled, but it's the responsibility of the user to create a config that builds. - Simplify misc aspects in the .mk file.] Signed-off-by: Thomas Petazzoni Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

vexpress-firmware: new package

2016-10-15T10:35:28+00:00

This commit adds a new package for the SCP (System Control Processor) firmware for the ARM reference platforms. There will most likely be other SCP firmware provided by other vendors, but they might be provided in a different form, so we for now create a vendor-specific package named vexpress-firmware. Since this firmware is used for booting, we create the package in boot/ and not in package/. The package simply installs a single pre-built binary file into the images directory. Signed-off-by: Joao Pinto [Thomas: - Rename the package from scpfirmware to vexpress-firmware. - Add a Config.in prompt for the package. - Remove the prompt-less Config.in options to select the Git repo and version. Since we only support the Vexpress firmware, there's no need for configurability here, so we just use the right Git repo/version in the .mk file. - Use $(INSTALL) -D to install the firmware file. - Add license information.] Signed-off-by: Thomas Petazzoni Reviewed-by: "Yann E. MORIN" [Thomas: add hash file, as suggested by Yann.] Signed-off-by: Thomas Petazzoni

boot/uboot: Call 'make all' unconditionally

2016-10-07T20:35:48+00:00

Since commit fad58cefa4a392b ("boot/uboot: allow to build multiple U-Boot images") the installation of SPL binary fails. For example, when building the mx6cubox_defconfig target we see: LD u-boot OBJCOPY u-boot-nodtb.bin COPY u-boot.bin MKIMAGE u-boot.img >>> uboot 2016.09.01 Installing to target >>> uboot 2016.09.01 Installing to images directory cp -dpf /home/fabio/buildroot/output/build/uboot-2016.09.01/u-boot.bin /home/fabio/buildroot/output/images/ cp -dpf /home/fabio/buildroot/output/build/uboot-2016.09.01/u-boot.img /home/fabio/buildroot/output/images/ cp -dpf /home/fabio/buildroot/output/build/uboot-2016.09.01/SPL /home/fabio/buildroot/output/images/ cp: cannot stat '/home/fabio/buildroot/output/build/uboot-2016.09.01/SPL': No such file or directory Instead of calling 'make all' only for the BR2_TARGET_UBOOT_FORMAT_DTB_IMG case, call 'make all' unconditionally so that the SPL target can also be installed. Signed-off-by: Fabio Estevam Signed-off-by: Thomas Petazzoni

u-boot: Fix building for ARC700

2016-09-25T21:24:27+00:00

With newer ARC toolchain obsolete -marcXXX were finally deperecated and so compiler throws errors now about unknown option. Solution is as simple as switching to more generic -mcu-XXX options. Which we do. Unfortunately that change in upstream U-Boot [1] happened right after v2016.09 was released an so we need to have that fix for v2016.07 which is mentioned in axs10x defconfigs and for the latest U-Boot release v2016.09 (which is selected by default if no defconfig is used). Once we deprecate either U-Boot version in U-Boot corresponding patch should be removed essentially. [1] http://git.denx.de/?p=u-boot.git;a=commit;h=7c8d81605302e7d7fdd3e7d8eb69302bddc64a2c Signed-off-by: Alexey Brodkin Cc: Thomas Petazzoni Cc: Peter Korsgaard Reviewed-by: Arnout Vandecappelle (Essensium/Mind) [Thomas: handle the U-Boot bump to 2016.09.01.] Signed-off-by: Thomas Petazzoni