mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] barebox: Copy TF-A binaries in to barebox firmware directory
Date: Thu, 13 Mar 2025 15:47:21 +0100	[thread overview]
Message-ID: <Z9Lv-fKJwjYnPjG7@pengutronix.de> (raw)
In-Reply-To: <Z9LrkbWgh1H7URcj@pengutronix.de>

On Thu, Mar 13, 2025 at 03:28:33PM +0100, Michael Tretter wrote:
> On Thu, 13 Mar 2025 13:21:50 +0100, 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
> > +
> 
> There is already a (underdocumented) mechanism to copy binaries to the
> barebox firmware directory: The PTXCONF_BAREBOX_FIRMWARE option and the
> world/inject call.
> 
> Enable PTXCONF_BAREBOX_FIRMWARE and add the filenames of the binaries
> that you want to install and their target location to the
> BAREBOX_INJECT_FILES variable. The inject mechanism copies the files
> from /usr/lib/firmware (BAREBOX_INJECT_PATH) to a specified location in
> the barebox build directory.

The patches[1] that introduced this feature also contained integration for
rockchip firmware. I did not apply those patches, but they are a good place
to look at if you need to do your own integration in your BSP.

Michael


[1] https://lore.ptxdist.org/ptxdist/20220129070330.2601433-1-michael.riesch@wolfvision.net/

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2025-03-13 14:47 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
2025-03-13 14:28 ` Michael Tretter
2025-03-13 14:47   ` Michael Olbrich [this message]

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=Z9Lv-fKJwjYnPjG7@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=benjamin.gaignard@collabora.com \
    --cc=m.tretter@pengutronix.de \
    --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