From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] barebox: Copy TF-A binaries in to barebox firmware directory
Date: Thu, 13 Mar 2025 13:52:21 +0100 [thread overview]
Message-ID: <f2f0e5e8-4df8-4c68-8385-4c875eb5e8a1@t2data.com> (raw)
In-Reply-To: <20250313122150.11021-1-benjamin.gaignard@collabora.com>
Hi Benjamin.
On 3/13/25 1:21 PM, Benjamin Gaignard wrote:
> If ARM trusted firmware option has been selected copy the
> generated bl32 binaries to barebox firmware directory so they
> can be included in barebox build process.
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> ---
> rules/barebox.make | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/rules/barebox.make b/rules/barebox.make
> index c0d9c5744..15c06d685 100644
> --- a/rules/barebox.make
> +++ b/rules/barebox.make
> @@ -119,6 +119,16 @@ ifdef PTXCONF_BAREBOX_EXTRA_ENV
> $(BAREBOX_BUILD_DIR)/.config; \
> fi
> endif
> +
> +ifdef PTXCONF_TF_A
> + mkdir -p $(BAREBOX_BUILD_DIR)/firmware/
> + @for i in `find $(PTXCONF_SYSROOT_TARGET)/usr/lib/firmware/ -maxdepth 1 \
> + -type f -name *-bl31.bin -printf "%f\n"`; do \
> + cp $(PTXCONF_SYSROOT_TARGET)/usr/lib/firmware/$$i $(BAREBOX_BUILD_DIR)/firmware/; \
> + cp $(PTXCONF_SYSROOT_TARGET)/usr/lib/firmware/$$i $(BAREBOX_DIR)/firmware/; \
> + done
> +endif
> +
I sort of get what you're trying to do, but this looks like all kinds of
weird. Naming, placement, constituents and targetinstall to pre-build?
I would suggest that a better interface for what is expected between
TF-A and BB is what is needed.
Regards,
Christian
> @$(call world/compile, BAREBOX)
> @$(call touch)
>
next prev parent reply other threads:[~2025-03-13 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 12:21 Benjamin Gaignard
2025-03-13 12:52 ` Christian Melki [this message]
2025-03-13 14:28 ` Michael Tretter
2025-03-13 14:47 ` 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=f2f0e5e8-4df8-4c68-8385-4c875eb5e8a1@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