DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Alexander Dahl <ada@thorsis.com>
Cc: distrokit@pengutronix.de, Lars Schmidt <l.schmidt@pengutronix.de>
Subject: Re: [DistroKit] [PATCH v2 0/4] platform: v8a: barebox: Untangle firmware inject files
Date: Sat, 26 Jul 2025 11:07:37 +0200	[thread overview]
Message-ID: <aISa2UyHoskrkhI_@pengutronix.de> (raw)
In-Reply-To: <20250523135815.2998753-1-ada@thorsis.com>

Hi Alex,

On Fri, May 23, 2025 at 03:58:11PM +0200, Alexander Dahl wrote:
> this is a one year later series with previously dropped patches from
> another series, and basically a follow-up to those mails:
>
> - <20240425-unlivable-approval-c55177db2d5c@thorsis.com>
> - <20250523081049.1693633-6-l.schmidt@pengutronix.de>
>
> Picking this up now, because this was almost ready last year already,
> but I did not manage to rework it for resubmission.  Not meant to be
> rude, but maybe suitable for discussing the right approach of firmware
> injection into different bootloader packages.
>
> When having another look, I think it was correct to drop v1, I did not
> go far enough with the first shot.  This is done now by patch 3/4 which
> separates the imx-firmware injects from the tf-a injects into separate
> fixup packages for barebox.  Patch 4/4 picks up an idea by Lars, please
> let me know when this should be attributed differently.
>
> Note, this is in conflict with the series "[PATCH 00/12] Add beagleplay
> support to DistroKit" sent earlier this week.
>
> Build tested twice on vanilla DistroKit _and_ in a custom BSP using
> DistroKit as a base layer and disabling most DistroKit boards.  Upper
> layer builds U-Boot for three different i.MX8/9 based boards, depending
> on both firmware-imx and tf-a.

I lost track of where we stand wrt. your series. However, I've now
merged the other series which was agreed between Lars and mol into next,
so this might be a good moment to re-check what's left.

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



      parent reply	other threads:[~2025-07-26  9:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 13:58 Alexander Dahl
2025-05-23 13:58 ` [DistroKit] [PATCH v2 1/4] platform: v8a: firmware-rockchip: Move barebox injects to separate package Alexander Dahl
2025-05-23 13:58 ` [DistroKit] [PATCH v2 2/4] platform: v8a: barebox: Remove extra host prog Alexander Dahl
2025-05-23 13:58 ` [DistroKit] [PATCH v2 3/4] platform: v8a: firmware-imx: Break out barebox injects to separate packages Alexander Dahl
2025-05-23 13:58 ` [DistroKit] [PATCH v2 4/4] platform: v8a: barebox: Inject tf-a binaries conditionally Alexander Dahl
2025-05-26  9:57 ` [DistroKit] [PATCH v2 0/4] platform: v8a: barebox: Untangle firmware inject files Lars Schmidt
2025-07-26  9:07 ` Robert Schwebel [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=aISa2UyHoskrkhI_@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=ada@thorsis.com \
    --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