From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: openembedded-core@lists.openembedded.org
Cc: yocto@pengutronix.de
Subject: Re: [OE-core][PATCH] barebox: upgrade 2026.03.1 -> 2026.04.0
Date: Mon, 20 Apr 2026 11:40:55 +0200 [thread overview]
Message-ID: <25b4ca00-a528-473b-9451-e3696ecc4a35@pengutronix.de> (raw)
In-Reply-To: <18A7DC2A7C609741.1451107@lists.openembedded.org>
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
Thanks!
Ahmad
>
> Release notes: https://lore.kernel.org/barebox/aeI471ZfStpltaM6@pengutronix.de
> Migration guide: https://barebox.org/doc/latest/migration-guides/migration-2026.04.0.html
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> meta/recipes-bsp/barebox/barebox-common.inc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-bsp/barebox/barebox-common.inc b/meta/recipes-bsp/barebox/barebox-common.inc
> index 9f615a82d48f..f736ca68e02f 100644
> --- a/meta/recipes-bsp/barebox/barebox-common.inc
> +++ b/meta/recipes-bsp/barebox/barebox-common.inc
> @@ -3,6 +3,6 @@ SECTION = "bootloaders"
>
> LIC_FILES_CHKSUM = "file://COPYING;md5=f5125d13e000b9ca1f0d3364286c4192"
>
> -PV = "2026.03.1"
> +PV = "2026.04.0"
> SRC_URI = "https://barebox.org/download/barebox-${PV}.tar.bz2"
> -SRC_URI[sha256sum] = "9e4b23720016bb934dc5ea36d4c33886a8a295445d290b99993d0b32caab6469"
> +SRC_URI[sha256sum] = "07fd3e3440c23e27d0094432f67827887fcc0e37d5fe24dc257c39b97c4294a0"
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#235526): https://lists.openembedded.org/g/openembedded-core/message/235526
> Mute This Topic: https://lists.openembedded.org/mt/118909793/4830399
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [a.fatoum@pengutronix.de]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
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 |
next parent reply other threads:[~2026-04-20 9:41 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 ` Ahmad Fatoum [this message]
2026-04-22 9:33 ` [OE-core][PATCH] barebox: upgrade 2026.03.1 -> 2026.04.0 Paul Barker
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=25b4ca00-a528-473b-9451-e3696ecc4a35@pengutronix.de \
--to=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