DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Lars Schmidt <l.schmidt@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH] fixup! beagleplay: fipimage: add fip image for K3
Date: Tue, 29 Jul 2025 15:15:58 +0200	[thread overview]
Message-ID: <aIjJjk8fdNAQYurU@pengutronix.de> (raw)
In-Reply-To: <20250729095843.2425494-1-l.schmidt@pengutronix.de>

fixed up

On Tue, Jul 29, 2025 at 11:58:43AM +0200, Lars Schmidt wrote:
> ---
> TF-A host tools contain fipimage tool, which is needed to build the fip image
> 
> 
>  configs/platform-v8a/platforms/image-fip-k3.in | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/configs/platform-v8a/platforms/image-fip-k3.in b/configs/platform-v8a/platforms/image-fip-k3.in
> index aff8196..cdd0447 100644
> --- a/configs/platform-v8a/platforms/image-fip-k3.in
> +++ b/configs/platform-v8a/platforms/image-fip-k3.in
> @@ -3,6 +3,7 @@
>  config IMAGE_FIP_K3
>  	tristate
>  	prompt "Generate images/k3.fip"
> +	select HOST_TF_A
>  	select BAREBOX
>  	select TF_A
>  	select FIRMWARE_TI
> -- 
> 2.39.5
> 
> 
> 

-- 
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:[~2025-07-29 13:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-26  8:54 [DistroKit] [PATCH v3 00/10] Add beagleplay support to DistroKit Lars Schmidt
2025-07-26  8:54 ` [DistroKit] [PATCH v3 01/10] v8a: barebox: bump version v2025.03.0 -> v2025.06.1 Lars Schmidt
2025-07-26  8:54 ` [DistroKit] [PATCH v3 02/10] beagleplay: k3: barebox needs part of tf-a firmware Lars Schmidt
2025-07-26  8:54 ` [DistroKit] [PATCH v3 03/10] tf-a: unify handling of firmware parts for barebox Lars Schmidt
2025-07-26  8:54 ` [DistroKit] [PATCH v3 04/10] beagleplay: firmware-ti: initial package Lars Schmidt
2025-07-26  8:54 ` [DistroKit] [PATCH v3 05/10] beagleplay: barebox: first stage bootloader for Cortex-R5 Lars Schmidt
2025-07-26  8:54 ` [DistroKit] [PATCH v3 06/10] beagleplay: fipimage: add fip image for K3 Lars Schmidt
2025-07-29  9:58   ` [DistroKit] [PATCH] fixup! " Lars Schmidt
2025-07-29 13:15     ` Robert Schwebel [this message]
2025-07-26  8:54 ` [DistroKit] [PATCH v3 07/10] beagleplay: add full image including bootloaders and rootfs Lars Schmidt
2025-07-26  8:54 ` [DistroKit] [PATCH v3 08/10] beagleplay: add initial kernel configuration Lars Schmidt
2025-07-26  8:54 ` [DistroKit] [PATCH v3 09/10] beagleplay: barebox: get second boot stage running Lars Schmidt
2025-07-26  8:54 ` [DistroKit] [PATCH v3 10/10] beagleplay: add initial platform config Lars Schmidt
2025-07-26  9:05 ` [DistroKit] [PATCH v3 00/10] Add beagleplay support to DistroKit Robert Schwebel
2025-07-29 13:02 ` [DistroKit] [PATCH 1/2] fixup! beagleplay: add initial platform config Lars Schmidt
2025-07-29 13:02   ` [DistroKit] [PATCH 2/2] fixup! beagleplay: add full image including bootloaders and rootfs Lars Schmidt
2025-07-29 13:34   ` [DistroKit] [PATCH 1/2] fixup! beagleplay: add initial platform config 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:
  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=aIjJjk8fdNAQYurU@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    --cc=l.schmidt@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