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

[Tom Rini]

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
-------------- 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/16a16772/attachment.sig>