From: Paul Barker <paul@pbarker.dev>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
openembedded-core@lists.openembedded.org
Cc: yocto@pengutronix.de
Subject: Re: [OE-core][PATCH] barebox: upgrade 2026.03.1 -> 2026.04.0
Date: Wed, 22 Apr 2026 10:33:41 +0100 [thread overview]
Message-ID: <e527213d5944e137dffca719318b9630a741c552.camel@pbarker.dev> (raw)
In-Reply-To: <25b4ca00-a528-473b-9451-e3696ecc4a35@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
On Mon, 2026-04-20 at 11:40 +0200, Ahmad Fatoum wrote:
> Hi,
>
> On 4/19/26 10:30 PM, Ahmad Fatoum wrote:
> > Main highlight of this release is the new devboot mechanism, which
> > allows overriding any combination of kernel, device tree and
> > initramfs in an existing boot flow with network-hosted files,
> > simplifying iterative development:
> >
> > https://www.barebox.org/doc/latest/user/devboot.html
> >
> > This release also restores compatibility with new TF-A versions acting
> > as SCMI clock provider, after TF-A v2.14 broke the SCMI v2.0 clock
> > protocol used by earlier barebox (and Linux <= v6.6).
>
> I see now that this barely missed the M3 freeze.
> barebox releases are monthly, but we were intending to provide long term
> support for v2026.04.0, so it would be great if this could make it in.
>
> The majority of new commits in this release are bugfixes[1] and even the
> highlighted feature resolves a boot-time breakage for barebox when
> compiled as EFI app.
>
> [1]: https://github.com/barebox/barebox/compare/v2026.03.0...v2026.04.0
Hi Ahmad,
Thanks for the extra information here. We've queued this one for the 6.0
M4 build as it's worthwhile to align with your LTS release when we know
you're actively involved.
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2026-04-22 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18A7DC2A7C609741.1451107@lists.openembedded.org>
2026-04-20 9:40 ` [OE-core][PATCH] barebox: upgrade 2026.03.1 -> 2026.04.0 Ahmad Fatoum
2026-04-22 9:33 ` Paul Barker [this message]
2026-04-19 20:30 Ahmad Fatoum
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=e527213d5944e137dffca719318b9630a741c552.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=a.fatoum@pengutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@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