Skip to contentSkip to conversation

barebox: upgrade 2026.03.1 -> 2026.04.0

PATCH Ahmad Fatoum 2 participants 2 messages Apr 20 – Apr 22 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi,

Quoted 10 lines · Ahmad Fatoum

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

Quoted 33 lines

Release notes: https://lore.kernel.org/barebox/[email protected]
Migration guide: https://barebox.org/doc/latest/migration-guides/migration-2026.04.0.html

---
 meta/recipes-bsp/barebox/barebox-common.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
meta/recipes-bsp/barebox/barebox-common.inc +2 -3
index 9f615a82d48f..f736ca68e02f 100644
@@ -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: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Signature · 4 lines
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 |
#2 lore raw
Quoted 18 lines · Ahmad Fatoum

Hi,

Quoted 10 lines · Ahmad Fatoum

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.

Quoted 5 lines

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,

Signature · 1 line
Paul Barker