DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [DistroKit] [PATCH] v8a: barebox: add missing dependency on TF_A for i.MX
Date: Thu,  1 Jun 2023 08:48:11 +0200	[thread overview]
Message-ID: <20230601064811.628050-1-a.fatoum@pengutronix.de> (raw)

Unlike firmware-rockchip, firmware-imx doesn't ship BL31 (TF-A). Instead
we configure the upstream TF-A rule to build images for i.MX8M Quad,
Mini and Plus.

With the switch to the upstream barebox rule, this dependency on TF-A
got lost breaking less-parallel fresh builds, so let's add it back.

Preferably, TF_A would be selected directly from the barebox rule's
Kconfig. There's a BAREBOX_DEPENDENCIES option for that, but I don't
know if it's possible to extend barebox.in without having to duplicate
it fully, so adding it to firmware-imx should suffice for now.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 configs/platform-v8a/rules/firmware-imx.in | 1 +
 1 file changed, 1 insertion(+)

diff --git a/configs/platform-v8a/rules/firmware-imx.in b/configs/platform-v8a/rules/firmware-imx.in
index 5f06a44416fa..c756b963e5dc 100644
--- a/configs/platform-v8a/rules/firmware-imx.in
+++ b/configs/platform-v8a/rules/firmware-imx.in
@@ -10,6 +10,7 @@ menuconfig FIRMWARE_IMX
 config BAREBOX_DEPENDENCIES
 	tristate
 	select FIRMWARE_IMX
+	select TF_A
 
 if FIRMWARE_IMX
 
-- 
2.39.2




             reply	other threads:[~2023-06-01  6:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01  6:48 Ahmad Fatoum [this message]
2023-06-01  6:49 ` Ahmad Fatoum
2023-06-01  7:05   ` Michael Olbrich
2023-06-01  7:11     ` Ahmad Fatoum
2023-06-01  9:15       ` Michael Olbrich
2023-06-01  9:31         ` Ahmad Fatoum
2023-06-01 12:23           ` 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=20230601064811.628050-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=distrokit@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