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

[Tom Rini]

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 at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20260127/c5c028d3/attachment.sig>