Skip to contentSkip to conversation

U-Boot v2025.10-rc2 released

ANN Tom Rini 1 participant 2 messages Aug 11, 2025 – Aug 12, 2025

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

Hey all,

It's release day and I have tagged and pushed things out. As this is rc2, the next branch is now open. Moving forward I'm asking that custodians ask themselves if changes are best merged for the October release, or for the January release. If there are regression fixes that people know of or otherwise big changes that should have come in by now, please speak up.

We're continuing with a community meeting following the release and once again this is the same time as the previous meeting. The meeting details itself are:
https://meet.google.com/btj-wgcg-euw
August 12th, 2025. 9am (GMT -06:00)

To join by phone:
https://meet.google.com/tel/btj-wgcg-euw?pin=1307528552322&hs=1

In terms of a rough changelog:
- The promised dts/upstream resync happened and we're on v6.16-dts.
- Enhancements, improvements and new platforms for Atmel, Marvell, Rockchip, STM32, SoCFPGA, Tegra, i.MX
- Networking (both legacy and lwIP) stack fixes.
- Addressing more issues found by smatch and removing unused code.

I continue to plan to do an rc release every two weeks and the final release will be 06 October 2025.

Thanks all!

Signature · 1 line
Tom
author
#1 lore raw
Quoted 9 lines · Tom Rini

Hey all,

It's release day and I have tagged and pushed things out. As this is rc2, the next branch is now open. Moving forward I'm asking that custodians ask themselves if changes are best merged for the October release, or for the January release. If there are regression fixes that people know of or otherwise big changes that should have come in by now, please speak up.

Quoted 5 lines

We're continuing with a community meeting following the release and once again this is the same time as the previous meeting. The meeting details itself are:
https://meet.google.com/btj-wgcg-euw
August 12th, 2025. 9am (GMT -06:00)

It was a short meeting again, and only a few people were able to attend. So I'm going to ask if another day / time would work for more people? Or are we just in summer vacation mode and this will change again in the fall?

That said:
- I noted rc2 is out and the next window is open. Things are looking on track for the release and I hope for pull requests for the next branch soon. Also, Coverity Scan is reporting a number of issues closed as the smatch fixes are also fixing those problems in many cases.
- I talked about "allyesconfig" a bit, and I will likely try and push this build a bit farther along, going by subdirectories. Andre asked what the reason is for doing allyesconfig and I explained that due to how we configure the build, it will always be sandbox only, and so the goal is to get more code under static analysis. Once it builds with what is in tree I hope people will want to get more of their architecture specific code (drivers first, most likely) building as well.
- Bryan Brattlof asked if there's a more generic mechanism today for being able to fire off events (remote proc firmware, memory tests, etc) and ensure they complete before moving on in the boot sequence. He's looking at prototyping this with UTHREADS currently and I suggested talking with NXP and STM32 people at least as they also have a number of remote proc stuff and might also have a similar problem and maybe solution.

Signature · 1 line
Tom