From: Jagan Teki <jagannadh.teki@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 01/11] arm-trusted-firmware: Build FIP for BL33
Date: Wed, 1 Nov 2017 19:05:43 +0100 [thread overview]
Message-ID: <1509559553-26544-2-git-send-email-jagan@amarulasolutions.com> (raw)
In-Reply-To: <1509559553-26544-1-git-send-email-jagan@amarulasolutions.com>
To build FIP for Juno, we need to set BL33 for non-BL33
there is no need to build the FIP, so this patch adjust
the make to handle both scenarios.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
boot/arm-trusted-firmware/arm-trusted-firmware.mk | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.mk b/boot/arm-trusted-firmware/arm-trusted-firmware.mk
index 7b1cc6e..5b4e3b0 100644
--- a/boot/arm-trusted-firmware/arm-trusted-firmware.mk
+++ b/boot/arm-trusted-firmware/arm-trusted-firmware.mk
@@ -28,21 +28,25 @@ ARM_TRUSTED_FIRMWARE_INSTALL_IMAGES = YES
ARM_TRUSTED_FIRMWARE_PLATFORM = $(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM))
+ARM_TRUSTED_FIRMWARE_CMDS += all
+
ARM_TRUSTED_FIRMWARE_MAKE_OPTS += \
CROSS_COMPILE="$(TARGET_CROSS)" \
- BL33=$(BINARIES_DIR)/u-boot.bin \
$(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES)) \
PLAT=$(ARM_TRUSTED_FIRMWARE_PLATFORM)
ifeq ($(BR2_TARGET_VEXPRESS_FIRMWARE),y)
-ARM_TRUSTED_FIRMWARE_MAKE_OPTS += SCP_BL2=$(BINARIES_DIR)/scp-fw.bin
ARM_TRUSTED_FIRMWARE_DEPENDENCIES += vexpress-firmware
+ARM_TRUSTED_FIRMWARE_MAKE_OPTS += \
+ BL33=$(BINARIES_DIR)/u-boot.bin \
+ SCP_BL2=$(BINARIES_DIR)/scp-fw.bin
+ARM_TRUSTED_FIRMWARE_CMDS += fip
endif
define ARM_TRUSTED_FIRMWARE_BUILD_CMDS
$(TARGET_CONFIGURE_OPTS) \
$(MAKE) -C $(@D) $(ARM_TRUSTED_FIRMWARE_MAKE_OPTS) \
- all fip
+ $(ARM_TRUSTED_FIRMWARE_CMDS)
endef
define ARM_TRUSTED_FIRMWARE_INSTALL_IMAGES_CMDS
--
1.9.1
next prev parent reply other threads:[~2017-11-01 18:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 18:05 [Buildroot] [PATCH v5 00/11] board: Add Allwinner A64/H5 boards Jagan Teki
2017-11-01 18:05 ` Jagan Teki [this message]
2017-11-01 18:05 ` [Buildroot] [PATCH v5 02/11] uboot: Add U-Boot-bundles-ATF support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 03/11] board: Add Bananapi M64 support Jagan Teki
[not found] ` <20171103181810202829132@banana-pi.com>
[not found] ` <2017110815285072387665@banana-pi.com>
2017-11-08 7:39 ` [Buildroot] 回复: " Thomas Petazzoni
2017-11-08 7:44 ` Jagan Teki
2017-12-02 14:58 ` [Buildroot] " Thomas Petazzoni
2017-12-02 15:10 ` Jagan Teki
2017-12-04 15:03 ` Andre Przywara
2017-12-04 15:18 ` Thomas Petazzoni
2017-11-01 18:05 ` [Buildroot] [PATCH v5 04/11] board: Add Pine64 support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 05/11] board: Add SoPine support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 06/11] board: Add FriendlyARM Nanopi A64 support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 07/11] board: Add FriendlyARM Nanopi NEO2 support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 08/11] board: Add Olimex A64-OLinuXino support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 09/11] board: Add Orangepi Win/Win Plus support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 10/11] board: Add Orangepi Prime support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 11/11] board: Add Orangepi Zero Plus2 support Jagan Teki
2017-11-06 9:39 ` [Buildroot] [PATCH v5 00/11] board: Add Allwinner A64/H5 boards Jagan Teki
2017-11-06 9:48 ` Thomas Petazzoni
2017-11-10 6:06 ` Jagan Teki
2017-11-10 12:33 ` nimaim
2017-11-23 16:27 ` Jagan Teki
2017-11-23 16:32 ` Thomas Petazzoni
2017-12-03 21:51 ` Thomas Petazzoni
2017-12-04 4:43 ` Jagan Teki
2017-12-04 8:04 ` Thomas Petazzoni
2017-12-19 20:48 ` Sergey Matyukevich
2017-12-20 9:05 ` Jagan Teki
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=1509559553-26544-2-git-send-email-jagan@amarulasolutions.com \
--to=jagannadh.teki@gmail.com \
--cc=buildroot@busybox.net \
/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