From: Arnout Vandecappelle <arnout@mind.be>
To: Changming Huang <jerry.huang@nxp.com>, buildroot@busybox.net
Cc: thomas.petazzoni@bootlin.com, heiko.thiery@gmail.com,
michael@walle.cc, geomatsi@gmail.com, matthew.weber@collins.com
Subject: Re: [Buildroot] [PATCH v5 5/9] boot/arm-trusted-firmware: allow additional make dependencies
Date: Thu, 6 Jan 2022 16:05:36 +0100 [thread overview]
Message-ID: <eab1c1bc-2de1-cde0-a0f3-cdab1e59e32d@mind.be> (raw)
In-Reply-To: <20200207083857.28058-5-jerry.huang@nxp.com>
On 07/02/2020 09:38, Changming Huang wrote:
> Allow specifying additional build dependencies for ATF.
>
> This might be more useful when using a custom git repository.
>
> For example, when using with the ATF repository from NXP QorIQ,
> the qoriq-rcw is used to build the pbl binary image.
This is not a very user-friendly way to do it. Since RCW support is something
that is in upstream ATF, I think it makes a whole lot more sense to make it an
explicit option. Something like:
config BR2_TARGET_ARM_TRUSTED_FIRMWARE_RCW
bool "Include RCW"
depends on BR2_HOST_QORIQ_RCW
help
Include the RCW in BL2.
That way you can also add the RCW=$(BINARIES_DIR)/PBL.bin automatically to the
variables (and this is an advantage of always calling it PBL.bin :-)
I've marked this patch as Changes Requested.
Regards,
Arnout
>
> Signed-off-by: Changming Huang <jerry.huang@nxp.com>
> ---
> changes since v4:
> 1. remove the option BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS.
> 2. modify the description.
>
> changes since v3:
> no changes.
>
> changes since v2:
> 1. introduce option BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS.
> 2. introduce option BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES.
> 3. rewrite the makefile with these two options
>
> changes since v1:
> 1. Use option BR2_PACKAGE_HOST_RCW_ATF as the condition for RCW used by ATF.
> ---
> boot/arm-trusted-firmware/Config.in | 5 +++++
> boot/arm-trusted-firmware/arm-trusted-firmware.mk | 3 +++
> 2 files changed, 8 insertions(+)
>
> diff --git a/boot/arm-trusted-firmware/Config.in b/boot/arm-trusted-firmware/Config.in
> index 373591d497..c9b74064d7 100644
> --- a/boot/arm-trusted-firmware/Config.in
> +++ b/boot/arm-trusted-firmware/Config.in
> @@ -142,6 +142,11 @@ config BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS
> E.G. When using the QorIQ custom ATF repository from NXP,
> the target 'pbl' can be used to build the pbl binary.
>
> +config BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES
> + string "Additional AFT dependencies"
> + help
> + Additional dependencies for ATF build, E.G. "host-qoriq-rcw"
> +
> config BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES
> string "Additional ATF build variables"
> help
> diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.mk b/boot/arm-trusted-firmware/arm-trusted-firmware.mk
> index bf1ac46cf6..43be2fef99 100644
> --- a/boot/arm-trusted-firmware/arm-trusted-firmware.mk
> +++ b/boot/arm-trusted-firmware/arm-trusted-firmware.mk
> @@ -92,6 +92,9 @@ endif
>
> ARM_TRUSTED_FIRMWARE_MAKE_TARGETS = all
>
> +ARM_TRUSTED_FIRMWARE_DEPENDENCIES += \
> + $(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES))
> +
> ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP),y)
> ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += fip
> ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-openssl
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-06 15:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 8:38 [Buildroot] [PATCH v5 1/9] package/nxp: new package directory Changming Huang
2020-02-07 8:38 ` [Buildroot] [PATCH v5 2/9] package/qoriq-rcw: move rcw into nxp and rename it Changming Huang
2020-04-14 9:35 ` Heiko Thiery
2020-12-16 21:02 ` Yann E. MORIN
2020-02-07 8:38 ` [Buildroot] [PATCH v5 3/9] package/qoriq-rcw: bump to version LSDK-19.09 Changming Huang
2020-02-07 8:38 ` [Buildroot] [PATCH v5 4/9] package/qoriq-rcw: add target rcw binary support Changming Huang
2022-01-06 14:48 ` Arnout Vandecappelle
2020-02-07 8:38 ` [Buildroot] [PATCH v5 5/9] boot/arm-trusted-firmware: allow additional make dependencies Changming Huang
2022-01-06 15:05 ` Arnout Vandecappelle [this message]
2020-02-07 8:38 ` [Buildroot] [PATCH v5 6/9] package/qoriq-cadence-dp-firmware: new package Changming Huang
2022-01-06 15:14 ` Michael Walle
2022-01-06 15:19 ` Arnout Vandecappelle
2020-02-07 8:38 ` [Buildroot] [PATCH v5 7/9] package/qoriq-rcw:Enable IIC5_PMUX and CLK_OUT_PMUX for GPIO Changming Huang
2022-01-06 15:54 ` Arnout Vandecappelle
2020-02-07 8:38 ` [Buildroot] [PATCH v5 8/9] package/nxp/qoriq-rcw: introduce BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE for boot mode Changming Huang
2022-01-06 15:55 ` Arnout Vandecappelle
2020-02-07 8:38 ` [Buildroot] [PATCH v5 9/9] board/nxp/ls1028ardb: new board Changming Huang
2022-01-06 16:27 ` Arnout Vandecappelle
2022-01-06 14:45 ` [Buildroot] [PATCH v5 1/9] package/nxp: new package directory Arnout Vandecappelle
2022-01-06 15:00 ` Michael Walle
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=eab1c1bc-2de1-cde0-a0f3-cdab1e59e32d@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
--cc=geomatsi@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=jerry.huang@nxp.com \
--cc=matthew.weber@collins.com \
--cc=michael@walle.cc \
--cc=thomas.petazzoni@bootlin.com \
/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