Skip to contentSkip to conversation

U-Boot v2026.04-rc1 released

ANN Tom Rini 4 participants 8 messages Jan 26 – Jan 27

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

Hey all,

So it's release day and I have tagged and pushed things out.

First and foremost, this is a bit rougher than I would like but I hope that doing the release will underscore the urgency of finishing some of these fixes. We now require for our own use to be given a correctly (8 byte) aligned device tree. This is done in a lot of cases. However:
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/#3640858
is needed to ensure that platforms that use a FIT image in the SPL phase work.
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
needs to be addressed further to fix the case of platforms which apply overlays in FIT images (SPL or OS). This series also shows that if your platform does not boot then SPL_MALLOC_F_LEN may be too small.
https://lore.kernel.org/u-boot/[email protected]/
contains some of the discussion around the case of SPL *not* enabling SPL_BSS_SEPARATE and so having an incorrectly sized empty BSS appeneded to the image.

So, that's the important state of things right now. Some platforms are broken. People helping to test the proposed fixes, or if needed, picking up the changes and posting the next version of them, would be appreciated.

We're continuing with a community meeting following the release and the calendar link is
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MHYzYzQ1dWh2bnRjcm80czVmcDczYmhsNThfMjAyNjAxMjdUMTUwMDAwWiA4OWJlN2I4MTMxMzZiZWMwNmE4M2RlNGRhNTk3NDVmMGFiZDExYzFiODM2MDYxYWUwNmMxYzdkYmNkMThkZjQxQGc&tmsrc=89be7b813136bec06a83de4da59745f0abd11c1b836061ae06c1c7dbcd18df41%40group.calendar.google.com&scp=ALL
and once again this is the same time as the previous meeting. The meeting details itself are:
https://meet.google.com/btj-wgcg-euw
January 26th, 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:
- We're on v6.17-dts for upstream device trees/bindings. The v6.18-dts tag will be too late for our release cycle so I expect people to be using the cherry-pick method to bring in dts changes as needed.
- Lots of platform updates. This is always the case with -rc1 and I never know which ones to emphasize.
- That said, we've removed ATAGS support from some platforms as it's very legacy these days.
- Lots of fixing of issues reported by Smatch.
- We now support clang-format and prefer that over the old scripts/Lindent option for formatting code.
- Continued work on improving our old pre-rST docs and converting them to rST.
- Fixes in our DFU, MMC, PMIC, USB, UBI, SCMI, UEFI and networking subsystems.
- Some cleanups and improvements to Falcon mode, with the aim of being able to support this feature in secure boot contexts.
- More patches required for "allyesconfig" to build have been merged, but some are still outstanding.

I continue to plan to do an rc release every two weeks and the final release will be 05 January 2026.

Thanks all!

Signature · 1 line
Tom
#1 lore raw

Hi Tom,

Thanks for the update.

Quoted 56 lines · Tom Rini

Hey all,

So it's release day and I have tagged and pushed things out.

First and foremost, this is a bit rougher than I would like but I hope that doing the release will underscore the urgency of finishing some of these fixes. We now require for our own use to be given a correctly (8 byte) aligned device tree. This is done in a lot of cases. However:
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/#3640858
is needed to ensure that platforms that use a FIT image in the SPL phase work.
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
needs to be addressed further to fix the case of platforms which apply overlays in FIT images (SPL or OS). This series also shows that if your platform does not boot then SPL_MALLOC_F_LEN may be too small.
https://lore.kernel.org/u-boot/[email protected]/
contains some of the discussion around the case of SPL *not* enabling SPL_BSS_SEPARATE and so having an incorrectly sized empty BSS appeneded to the image.

So, that's the important state of things right now. Some platforms are broken. People helping to test the proposed fixes, or if needed, picking up the changes and posting the next version of them, would be appreciated.

We're continuing with a community meeting following the release and the calendar link is
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MHYzYzQ1dWh2bnRjcm80czVmcDczYmhsNThfMjAyNjAxMjdUMTUwMDAwWiA4OWJlN2I4MTMxMzZiZWMwNmE4M2RlNGRhNTk3NDVmMGFiZDExYzFiODM2MDYxYWUwNmMxYzdkYmNkMThkZjQxQGc&tmsrc=89be7b813136bec06a83de4da59745f0abd11c1b836061ae06c1c7dbcd18df41%40group.calendar.google.com&scp=ALL
and once again this is the same time as the previous meeting. The meeting details itself are:
https://meet.google.com/btj-wgcg-euw
January 26th, 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:
- We're on v6.17-dts for upstream device trees/bindings. The v6.18-dts tag will be too late for our release cycle so I expect people to be using the cherry-pick method to bring in dts changes as needed.
- Lots of platform updates. This is always the case with -rc1 and I never know which ones to emphasize.
- That said, we've removed ATAGS support from some platforms as it's very legacy these days.
- Lots of fixing of issues reported by Smatch.
- We now support clang-format and prefer that over the old scripts/Lindent option for formatting code.
- Continued work on improving our old pre-rST docs and converting them to rST.
- Fixes in our DFU, MMC, PMIC, USB, UBI, SCMI, UEFI and networking subsystems.
- Some cleanups and improvements to Falcon mode, with the aim of being able to support this feature in secure boot contexts.
- More patches required for "allyesconfig" to build have been merged, but some are still outstanding.

Quoted 2 lines

I continue to plan to do an rc release every two weeks and the final release will be 05 January 2026.

I guess you mean 06 April 2026 as stated in
https://docs.u-boot.org/en/latest/develop/release_cycle.html#future-releases

Quoted 5 lines

Thanks all!

Signature · 1 line
Tom
author
#2 lore raw
Quoted 62 lines · Mattijs Korpershoek

Hi Tom,

Thanks for the update.

Quoted 56 lines · Tom Rini

Hey all,

So it's release day and I have tagged and pushed things out.

First and foremost, this is a bit rougher than I would like but I hope that doing the release will underscore the urgency of finishing some of these fixes. We now require for our own use to be given a correctly (8 byte) aligned device tree. This is done in a lot of cases. However:
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/#3640858
is needed to ensure that platforms that use a FIT image in the SPL phase work.
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
needs to be addressed further to fix the case of platforms which apply overlays in FIT images (SPL or OS). This series also shows that if your platform does not boot then SPL_MALLOC_F_LEN may be too small.
https://lore.kernel.org/u-boot/[email protected]/
contains some of the discussion around the case of SPL *not* enabling SPL_BSS_SEPARATE and so having an incorrectly sized empty BSS appeneded to the image.

So, that's the important state of things right now. Some platforms are broken. People helping to test the proposed fixes, or if needed, picking up the changes and posting the next version of them, would be appreciated.

We're continuing with a community meeting following the release and the calendar link is
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MHYzYzQ1dWh2bnRjcm80czVmcDczYmhsNThfMjAyNjAxMjdUMTUwMDAwWiA4OWJlN2I4MTMxMzZiZWMwNmE4M2RlNGRhNTk3NDVmMGFiZDExYzFiODM2MDYxYWUwNmMxYzdkYmNkMThkZjQxQGc&tmsrc=89be7b813136bec06a83de4da59745f0abd11c1b836061ae06c1c7dbcd18df41%40group.calendar.google.com&scp=ALL
and once again this is the same time as the previous meeting. The meeting details itself are:
https://meet.google.com/btj-wgcg-euw
January 26th, 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:
- We're on v6.17-dts for upstream device trees/bindings. The v6.18-dts tag will be too late for our release cycle so I expect people to be using the cherry-pick method to bring in dts changes as needed.
- Lots of platform updates. This is always the case with -rc1 and I never know which ones to emphasize.
- That said, we've removed ATAGS support from some platforms as it's very legacy these days.
- Lots of fixing of issues reported by Smatch.
- We now support clang-format and prefer that over the old scripts/Lindent option for formatting code.
- Continued work on improving our old pre-rST docs and converting them to rST.
- Fixes in our DFU, MMC, PMIC, USB, UBI, SCMI, UEFI and networking subsystems.
- Some cleanups and improvements to Falcon mode, with the aim of being able to support this feature in secure boot contexts.
- More patches required for "allyesconfig" to build have been merged, but some are still outstanding.

Quoted 5 lines
Quoted 2 lines

I continue to plan to do an rc release every two weeks and the final release will be 05 January 2026.

I guess you mean 06 April 2026 as stated in
https://docs.u-boot.org/en/latest/develop/release_cycle.html#future-releases

Yes, thanks. It does show sometimes that I edit previous release emails :)

Signature · 1 line
Tom
#3 lore raw
In reply to Tom Rini

Hi Tom, all,

Quoted 33 lines · Tom Rini

Hey all,

So it's release day and I have tagged and pushed things out.

First and foremost, this is a bit rougher than I would like but I hope that doing the release will underscore the urgency of finishing some of these fixes. We now require for our own use to be given a correctly (8 byte) aligned device tree. This is done in a lot of cases. However:
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/#3640858
is needed to ensure that platforms that use a FIT image in the SPL phase work.
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
needs to be addressed further to fix the case of platforms which apply overlays in FIT images (SPL or OS). This series also shows that if your platform does not boot then SPL_MALLOC_F_LEN may be too small.
https://lore.kernel.org/u-boot/[email protected]/
contains some of the discussion around the case of SPL *not* enabling SPL_BSS_SEPARATE and so having an incorrectly sized empty BSS appeneded to the image.

So, that's the important state of things right now. Some platforms are broken. People helping to test the proposed fixes, or if needed, picking up the changes and posting the next version of them, would be appreciated.

We're continuing with a community meeting following the release and the calendar link is
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MHYzYzQ1dWh2bnRjcm80czVmcDczYmhsNThfMjAyNjAxMjdUMTUwMDAwWiA4OWJlN2I4MTMxMzZiZWMwNmE4M2RlNGRhNTk3NDVmMGFiZDExYzFiODM2MDYxYWUwNmMxYzdkYmNkMThkZjQxQGc&tmsrc=89be7b813136bec06a83de4da59745f0abd11c1b836061ae06c1c7dbcd18df41%40group.calendar.google.com&scp=ALL
and once again this is the same time as the previous meeting. The meeting details itself are:
https://meet.google.com/btj-wgcg-euw
January 26th, 2025. 9am (GMT -06:00)

Quoted 5 lines

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

In terms of a rough changelog:
- We're on v6.17-dts for upstream device trees/bindings. The v6.18-dts

We're on v6.18-dts already, so increment one in both versions above to have the current state.

Cheers,
Quentin

author
#4 lore raw
Quoted 36 lines · Quentin Schulz

Hi Tom, all,

Quoted 33 lines · Tom Rini

Hey all,

So it's release day and I have tagged and pushed things out.

First and foremost, this is a bit rougher than I would like but I hope that doing the release will underscore the urgency of finishing some of these fixes. We now require for our own use to be given a correctly (8 byte) aligned device tree. This is done in a lot of cases. However:
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/#3640858
is needed to ensure that platforms that use a FIT image in the SPL phase work.
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
needs to be addressed further to fix the case of platforms which apply overlays in FIT images (SPL or OS). This series also shows that if your platform does not boot then SPL_MALLOC_F_LEN may be too small.
https://lore.kernel.org/u-boot/[email protected]/
contains some of the discussion around the case of SPL *not* enabling SPL_BSS_SEPARATE and so having an incorrectly sized empty BSS appeneded to the image.

So, that's the important state of things right now. Some platforms are broken. People helping to test the proposed fixes, or if needed, picking up the changes and posting the next version of them, would be appreciated.

We're continuing with a community meeting following the release and the calendar link is
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MHYzYzQ1dWh2bnRjcm80czVmcDczYmhsNThfMjAyNjAxMjdUMTUwMDAwWiA4OWJlN2I4MTMxMzZiZWMwNmE4M2RlNGRhNTk3NDVmMGFiZDExYzFiODM2MDYxYWUwNmMxYzdkYmNkMThkZjQxQGc&tmsrc=89be7b813136bec06a83de4da59745f0abd11c1b836061ae06c1c7dbcd18df41%40group.calendar.google.com&scp=ALL
and once again this is the same time as the previous meeting. The meeting details itself are:
https://meet.google.com/btj-wgcg-euw
January 26th, 2025. 9am (GMT -06:00)

Quoted 8 lines
Quoted 5 lines

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

In terms of a rough changelog:
- We're on v6.17-dts for upstream device trees/bindings. The v6.18-dts

We're on v6.18-dts already, so increment one in both versions above to have the current state.

... Oh blah. I knew I got sidetracked and would forget something. I was looking at the final linker / dtb problem (that Fabio reported) and so forgot entirely to write a changelog.

Signature · 1 line
Tom
#5 lore raw
Quoted 3 lines · Tom Rini

... Oh blah. I knew I got sidetracked and would forget something. I was looking at the final linker / dtb problem (that Fabio reported) and so forgot entirely to write a changelog.

BTW, I tested your
https://github.com/u-boot/u-boot/commit/380ddb473c6bdf87e66c0fb93e256d1e233c6f5b

It does not work on RV1103:

$ cat spl/u-boot-spl.map | grep __bss_end
                0x0000000000015f18                __bss_end = .
                0x0000000000000268                __bss_size =
(__bss_end - __bss_start)
$ hexdump -Cv spl/u-boot-spl.bin | grep 'd0 0d fe ed'
000029f0  d0 0d fe ed 00 29 05 db  8a 18 03 d2 43 6a 1b ba  |.....)......Cj..|
00015f10  00 00 00 00 d0 0d fe ed  00 00 0a 43 00 00 00 38  |...........C...8|

FDT_MAGIC appears at 15f14 instead of 15f18.

I saw it was reverted later.

Please let me know if there is anything you want me to test.

author
#6 lore raw
Quoted 20 lines · Fabio Estevam
Quoted 3 lines · Tom Rini

... Oh blah. I knew I got sidetracked and would forget something. I was looking at the final linker / dtb problem (that Fabio reported) and so forgot entirely to write a changelog.

BTW, I tested your
https://github.com/u-boot/u-boot/commit/380ddb473c6bdf87e66c0fb93e256d1e233c6f5b

It does not work on RV1103:

$ cat spl/u-boot-spl.map | grep __bss_end
                0x0000000000015f18                __bss_end = .
                0x0000000000000268                __bss_size =
(__bss_end - __bss_start)
$ hexdump -Cv spl/u-boot-spl.bin | grep 'd0 0d fe ed'
000029f0  d0 0d fe ed 00 29 05 db  8a 18 03 d2 43 6a 1b ba  |.....)......Cj..|
00015f10  00 00 00 00 d0 0d fe ed  00 00 0a 43 00 00 00 38  |...........C...8|
Quoted 5 lines

FDT_MAGIC appears at 15f14 instead of 15f18.

I saw it was reverted later.

Please let me know if there is anything you want me to test.

Yeah, I pushed a few things by very much accident through to master, and reverted them.

Signature · 1 line
Tom
author
#7 lore raw
In reply to Tom Rini
Quoted 25 lines · Tom Rini

Hey all,

So it's release day and I have tagged and pushed things out.

First and foremost, this is a bit rougher than I would like but I hope that doing the release will underscore the urgency of finishing some of these fixes. We now require for our own use to be given a correctly (8 byte) aligned device tree. This is done in a lot of cases. However:
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/#3640858
is needed to ensure that platforms that use a FIT image in the SPL phase work.
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
needs to be addressed further to fix the case of platforms which apply overlays in FIT images (SPL or OS). This series also shows that if your platform does not boot then SPL_MALLOC_F_LEN may be too small.
https://lore.kernel.org/u-boot/[email protected]/
contains some of the discussion around the case of SPL *not* enabling SPL_BSS_SEPARATE and so having an incorrectly sized empty BSS appeneded to the image.

So, that's the important state of things right now. Some platforms are broken. People helping to test the proposed fixes, or if needed, picking up the changes and posting the next version of them, would be appreciated.

Quoted 7 lines

We're continuing with a community meeting following the release and the calendar link is
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MHYzYzQ1dWh2bnRjcm80czVmcDczYmhsNThfMjAyNjAxMjdUMTUwMDAwWiA4OWJlN2I4MTMxMzZiZWMwNmE4M2RlNGRhNTk3NDVmMGFiZDExYzFiODM2MDYxYWUwNmMxYzdkYmNkMThkZjQxQGc&tmsrc=89be7b813136bec06a83de4da59745f0abd11c1b836061ae06c1c7dbcd18df41%40group.calendar.google.com&scp=ALL
and once again this is the same time as the previous meeting. The meeting details itself are:
https://meet.google.com/btj-wgcg-euw
January 26th, 2025. 9am (GMT -06:00)

My apologies everyone. I did notice that Google changed the calendar link when working on this email but did not notice that the meeting link itself changed too. The call was relatively short and just covered the above issues, that we hope to move to OSU OSL hosting for infrastructure soon, and that Marek is working on something for streaming larger files via network and writing to storage. Also, Marek (and SFC) will be at FOSDEM if anyone else is attending.

[snip]

Quoted 1 line

In terms of a rough changelog:

... this was wrong, and not updated from v2026.01-rc1. A correct changelog (which I need for the final release itself, too!):

- Lots of platform updates, including but not limited to: TI K3, NXP i.MX, STM32, NXP Layerscape, Altera SoCFPGA, various AMD/Xilinx families, MediaTek, TI AM33xx, Qualcomm, ADI SC5xx, Allwinner
- Lots of subsystem updates, including but not limited to: EFI Loader, Networking, UFS, DFU, MMC, Clock, Power, Documentation, i2c
- Assorted code and testing cleanups
- CI is now running on Ubuntu 24.04 "Noble", and also now supports "make allyesconfig" as part of the build. CI now also has a limited set of hardware platforms supported again, via the "Sage Lab".
- We have re-synced with upstream dtc v1.7.2-35-g52f07dcca47c and in turn now require 8 byte dtb alignment ourselves as the spec requires.
- Much of the legacy LED code is now removed, with just a few more things left to verify before final removal.
- FIT image signing with some proprietary hardware engines is now supported.

Signature · 1 line
Tom