DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH 3/8] genimage: patch in Firmware Image Package (FIP) support
Date: Mon, 5 Sep 2022 16:28:57 +0200	[thread overview]
Message-ID: <YxYHqY+K2llWwXum@pengutronix.de> (raw)
In-Reply-To: <20220725120445.1295669-3-a.fatoum@pengutronix.de>

On Mon, Jul 25, 2022 at 02:04:40PM +0200, Ahmad Fatoum wrote:
> genimage master has support for calling fiptool, which makes it
> straight-forward to generate eMMC boot partition images with the
> same genimage.config generating the image for the user area.
> TF-A also has a fip target that can call fiptool for us, but is only
> works when generating a single bootloader image, but we generate
> multiple images, so we can't reuse the current tf-a rule as is.
> One more option would be to write a custom image rule, but as genimage
> master has support, let's just backport the patch. The autogen.sh is
> necessary, because we touch Makefile.am and we want autogen to rerun to
> account for changes between our host autotools and the one used to
> build the shipped files.
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
>  ...d-Firmware-Image-Package-FIP-support.patch | 311 ++++++++++++++++++
>  patches/genimage-15/series                    |   1 +
>  2 files changed, 312 insertions(+)
>  create mode 100644 patches/genimage-15/0001-Add-Firmware-Image-Package-FIP-support.patch
>  create mode 100644 patches/genimage-15/series

As mol has meanwhile released genimage-16 (not in ptxdist yet), let's
update to that version, instead of patching genimage-15.

Changed in next.

Pengutronix e.K.                           | Dipl.-Ing. Robert Schwebel  |
Steuerwalder Str. 21                       | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |

  reply	other threads:[~2022-09-05 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 12:04 [DistroKit] [PATCH 1/8] v7a: tf-a: don't compile in unused NAND/NOR boot in FSBL Ahmad Fatoum
2022-07-25 12:04 ` [DistroKit] [PATCH 2/8] v7a: tf-a: update to v2.7 Ahmad Fatoum
2022-07-25 12:04 ` [DistroKit] [PATCH 3/8] genimage: patch in Firmware Image Package (FIP) support Ahmad Fatoum
2022-09-05 14:28   ` Robert Schwebel [this message]
2022-07-25 12:04 ` [DistroKit] [PATCH 4/8] v7a: barebox-stm32mp: start collecting device tree blobs Ahmad Fatoum
2022-07-25 12:04 ` [DistroKit] [PATCH 5/8] v7a: tf-a: start collecting FIP image components Ahmad Fatoum
2022-07-25 12:04 ` [DistroKit] [PATCH 6/8] v7a: tf-a: switch to FIP image Ahmad Fatoum
2022-07-25 12:04 ` [DistroKit] [PATCH 7/8] v7a: barebox: update v2022.04.0 → v2022.06.0 Ahmad Fatoum
2022-07-25 12:04 ` [DistroKit] [PATCH 8/8] v7a: barebox: ignore card-detect for booted SD-Card Ahmad Fatoum
2022-09-05 13:51 ` [DistroKit] [PATCH 1/8] v7a: tf-a: don't compile in unused NAND/NOR boot in FSBL Robert Schwebel

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YxYHqY+K2llWwXum@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=distrokit@pengutronix.de \


* 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