path: root/configs/arm_juno_defconfig
Commit message (Collapse)AuthorAgeFilesLines
* arm-trusted-firmware: add BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_AS_BL33Gravatar Thomas Petazzoni2017-12-081-0/+1
| | | | | | | | | | | | | | | | | | | | | ATF can be used in different ways: - ATF encapsulates U-Boot as the BL33, which is what is done on ARM Juno (currently supported in Buildroot) and Marvell platforms (soon to be supported) - U-Boot encapsulates ATF's BL31, which is what is done on Allwinner ARM64 platforms. Until now we were assumming the former was always the case, but obviously it isn't. Therefore, this patch adds an option that allows to explicitly tell ATF that it encapsulates U-Boot as its BL33. We adapt the only defconfig that uses ATF so that it enables this option as appropriate. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* arm-trusted-firmware: add option to enable/disable building FIP imageGravatar Thomas Petazzoni2017-12-081-0/+1
| | | | | | | | | | | | | | | | | | | | Currently, our arm-trusted-firmware unconditionally builds a FIP (Firmware Image Package). While this is often needed on platforms where ATF encapsulates U-Boot, it is not the case on some other platforms where it's U-Boot that encapsulates parts of ATF. In order to prepare the support for the later platforms, we make building the FIP image optional, and update the only defconfig we have that uses ARM Trusted Firmware. Note: we considered adding a "default y" here to preserve backward compatibility, but there really isn't any default that is sane: whether a FIP image needs to be built or not is purely platform specific. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: Sergey Matyukevich <geomatsi@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* configs/arm_juno: use official kernel tarballGravatar Thomas Petazzoni2016-10-151-3/+2
| | | | | | | | | | Since commit 0924208839336f1a1bb29eb1a627005ba6b9065d ("configs/arm_juno: use 4.6 mainline kernel"), we're using a mainline kernel for the ARM Juno board. But we're still fetching it from a Git repository, which is not really efficient, so let's switch to use a tarball instead. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* configs/arm_juno: add the bootloader buildGravatar Joao Pinto2016-10-151-0/+10
| | | | | | | | | | | Thanks to the recent addition of the vexpress-firmware and arm-trusted-firmware packages, this commit improves the ARM Juno defconfig to also build a bootloader. Signed-off-by: Joao Pinto <jpinto@synopsys.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* configs/arm_juno: use 4.6 mainline kernelGravatar Joao Pinto2016-06-091-5/+3
| | | | | | Signed-off-by: Joao Pinto <jpinto@synopsys.com> [Thomas: use BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_6.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* configs/arm_juno: add support for Juno r2Gravatar Joao Pinto2016-06-091-1/+1
| | | | | Signed-off-by: Joao Pinto <jpinto@synopsys.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* board: add support for ARM Juno r0 and r1 Development BoardsGravatar Joao Pinto2016-02-041-0/+14
The Juno ARM Development Platform (ADP) is a software development platform for ARMv8-A, it includes the Juno Versatile Express board and an ARMv8-A reference software port available through Linaro. Signed-off-by: Joao Pinto <jpinto@synopsys.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>