[ANN] U-Boot v2026.04-rc1 released

[ANN] U-Boot v2026.04-rc1 released

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 3127 bytes --]

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/20260122172247.2995437-1-b-padhi@ti.com/#3640858
is needed to ensure that platforms that use a FIT image in the SPL phase
work.
https://patchwork.ozlabs.org/project/uboot/patch/20260120153314.95091-2-jamie.gibbons@microchip.com/
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/20260123161907.392211-1-festevam@gmail.com/
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!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [ANN] U-Boot v2026.04-rc1 released

[Mattijs Korpershoek]

Hi Tom,

Thanks for the update.

On Mon, Jan 26, 2026 at 14:45, Tom Rini <trini@konsulko.com> wrote:

> 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/20260122172247.2995437-1-b-padhi@ti.com/#3640858
> is needed to ensure that platforms that use a FIT image in the SPL phase
> work.
> https://patchwork.ozlabs.org/project/uboot/patch/20260120153314.95091-2-jamie.gibbons@microchip.com/
> 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/20260123161907.392211-1-festevam@gmail.com/
> 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.

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

>
> Thanks all!
>
> -- 
> Tom

Re: [ANN] U-Boot v2026.04-rc1 released

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 3737 bytes --]

On Tue, Jan 27, 2026 at 09:03:07AM +0100, Mattijs Korpershoek wrote:
> Hi Tom,
> 
> Thanks for the update.
> 
> On Mon, Jan 26, 2026 at 14:45, Tom Rini <trini@konsulko.com> wrote:
> 
> > 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/20260122172247.2995437-1-b-padhi@ti.com/#3640858
> > is needed to ensure that platforms that use a FIT image in the SPL phase
> > work.
> > https://patchwork.ozlabs.org/project/uboot/patch/20260120153314.95091-2-jamie.gibbons@microchip.com/
> > 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/20260123161907.392211-1-festevam@gmail.com/
> > 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.
> 
> 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
:)

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [ANN] U-Boot v2026.04-rc1 released

[Quentin Schulz]

Hi Tom, all,

On 1/26/26 9:45 PM, Tom Rini wrote:
> 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/20260122172247.2995437-1-b-padhi@ti.com/#3640858
> is needed to ensure that platforms that use a FIT image in the SPL phase
> work.
> https://patchwork.ozlabs.org/project/uboot/patch/20260120153314.95091-2-jamie.gibbons@microchip.com/
> 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/20260123161907.392211-1-festevam@gmail.com/
> 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

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

Cheers,
Quentin

Re: [ANN] U-Boot v2026.04-rc1 released

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 2670 bytes --]

On Tue, Jan 27, 2026 at 11:10:50AM +0100, Quentin Schulz wrote:
> Hi Tom, all,
> 
> On 1/26/26 9:45 PM, Tom Rini wrote:
> > 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/20260122172247.2995437-1-b-padhi@ti.com/#3640858
> > is needed to ensure that platforms that use a FIT image in the SPL phase
> > work.
> > https://patchwork.ozlabs.org/project/uboot/patch/20260120153314.95091-2-jamie.gibbons@microchip.com/
> > 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/20260123161907.392211-1-festevam@gmail.com/
> > 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
> 
> 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.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [ANN] U-Boot v2026.04-rc1 released

[Fabio Estevam]

On Tue, Jan 27, 2026 at 11:59 AM Tom Rini <trini@konsulko.com> wrote:

> ... 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.

Re: [ANN] U-Boot v2026.04-rc1 released

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

On Tue, Jan 27, 2026 at 01:38:10PM -0300, Fabio Estevam wrote:
> On Tue, Jan 27, 2026 at 11:59 AM Tom Rini <trini@konsulko.com> wrote:
> 
> > ... 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.

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

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [ANN] U-Boot v2026.04-rc1 released

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 3603 bytes --]

On Mon, Jan 26, 2026 at 02:45:48PM -0600, Tom Rini wrote:

> 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/20260122172247.2995437-1-b-padhi@ti.com/#3640858
> is needed to ensure that platforms that use a FIT image in the SPL phase
> work.
> https://patchwork.ozlabs.org/project/uboot/patch/20260120153314.95091-2-jamie.gibbons@microchip.com/
> 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/20260123161907.392211-1-festevam@gmail.com/
> 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)

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]
> 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.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]