mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Felix Mellmann <flix.ptxdist@benfm.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Best practice integrating firmwares in U-Boot builds
Date: Wed, 25 May 2022 20:55:23 +0200	[thread overview]
Message-ID: <20220525185523.GG1615@pengutronix.de> (raw)
In-Reply-To: <8f755f04-56ea-127b-ce7e-48018a7bc1b8@benfm.de>

Hi Felix,

On Wed, May 25, 2022 at 05:22:41PM +0200, Felix Mellmann wrote:
> Hi,
> 
> when I tried to set up a PTXdist environment for a NXP i.MX8MP based board
> (Phytec phyBoard Pollux) I stumbled across the need to provide firmware
> images during the U-Boot build process (LPDDR4 training data and TF-A BL31
> firmware).
> 
> Is there a best practice on how to provide those firmwares during build?
> Currently I helped myself and modified u-boot.make to copy the firmware
> files at the very beginning of the compile stage to the build directory...

See here:
https://lore.ptxdist.org/ptxdist/20220129070330.2601433-1-michael.riesch@wolfvision.net/

These patches solve the problem for the Rockchip TF-A binary blobs
integrated into barebox. The helper introduced there is generic and
the solution could look similar for U-Boot I guess.

Sascha

-- 
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 |



      parent reply	other threads:[~2022-05-25 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25 15:22 Felix Mellmann
2022-05-25 15:53 ` Christian Melki
2022-05-25 15:56 ` Christian Melki
2022-05-25 18:55 ` Sascha Hauer [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=20220525185523.GG1615@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=flix.ptxdist@benfm.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