From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH v2] U-Boot: Add TF-A dependency option.
Date: Mon, 29 Nov 2021 20:49:02 +0100 [thread overview]
Message-ID: <20211129194903.596814-1-christian.melki@t2data.com> (raw)
Let U-Boot depend on TF-A firmwares for inclusion.
TF-A firmwares are a common thing on various machines.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
platforms/u-boot.in | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/platforms/u-boot.in b/platforms/u-boot.in
index 4ddf3b3fb..410391fe8 100644
--- a/platforms/u-boot.in
+++ b/platforms/u-boot.in
@@ -2,6 +2,7 @@
menuconfig U_BOOT
select BOOTLOADER
+ select TF_A if U_BOOT_USE_TF_A
prompt "U-Boot "
bool
@@ -71,12 +72,19 @@ config U_BOOT_CONFIG
endif
+config U_BOOT_USE_TF_A
+ prompt "Include TF-A firmwares in U-Boot."
+ bool
+ help
+ Generate TF-A (ARM Trusted Firmwares type A) to include in u-boot.
+
config U_BOOT_CUSTOM_MAKE_OPTS
prompt "Custom make options"
string
help
List of custom make options passed at build time. Can be
- used for example to pass a DEVICE_TREE= value.
+ used for example to pass a DEVICE_TREE= value or passing
+ TF-A firmware, BL31=${PTXDIST_PLATFORMDIR}/path-to/bl31.bin
choice
prompt "Generate environment image"
--
2.30.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2021-11-29 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 19:49 Christian Melki [this message]
2021-11-29 19:49 ` [ptxdist] [PATCH v2] U-Boot: Add option to disable OOT builds Christian Melki
2021-11-30 5:43 ` Alexander Dahl
2021-11-30 8:04 ` Alexander Dahl
2022-02-04 8:20 ` [ptxdist] [PATCH v2] U-Boot: Add TF-A dependency option Michael Olbrich
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=20211129194903.596814-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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