[AUH] barebox-tools: upgrading to 2026.10.0 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe(s) *barebox-tools* to *2026.10.0* has Succeeded.

Next steps:
    - apply the patch: git am 0001-barebox-tools-upgrade-2026.09.0-2026.10.0.patch
    - check the changes to upstream patches and summarize them in the commit message,
    - compile an image that contains the package
    - perform some basic sanity tests
    - amend the patch and sign it off: git commit -s --reset-author --amend
    - send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update failures.
Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-- >8 --
From 45a2d32a19feebea74dd96a40bc7fbaa7ee032c1 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Wed, 21 Oct 2026 05:16:42 +0000
Subject: [PATCH] barebox-tools: upgrade 2026.09.0 -> 2026.10.0

Release v2025.01.0
==================

Layerscape
----------

Support for the NXP-specific PPA Secure Monitor has been removed in
favor of ARM Trusted Firmware-A as the former has been long unmaintained.

I2C Adapter numbering
---------------------

``i2c0`` to ``i2c31`` are now reserved for I2C adapters with device tree
aliases. Do not rely on a fixed numbering for other non-aliased adapters.

OP-TEE for Rockchip
-------------------

The BL32 firmware images are now called ``firmware/rk3XXX-bl32.bin``
instead of ``firmware/rk3XXX-op-tee.bin``. Raw OP-TEE binaries without
a header now use the load address the vendor blobs are hardcoded to
run at instead of the previous ``0x200000``. To override, use an OP-TEE
image with a header specifying the correct load address.

TFTP
----

The default TFTP window size has been reverted to 1 as many network
drivers couldn't cope with the increased throughput.
This can be reverted by setting ``CONFIG_FS_TFTP_MAX_WINDOW_SIZE``
or at runtime via the
:ref:`global.tftp.windowsize <magicvar_global_tftp_windowsize>` variable.

Release v2025.02.0
==================

Environment Auto-Probe
----------------------

A new magic variable ``global.env.autoprobe``
now controls whether barebox
will automatically probe known block devices for a GPT barebox environment
partition if no environment was specified by other means.

The variable defaults to ``0`` (false) if ``CONFIG_INSECURE`` is disabled.

The most secure option remains disabling ``CONFIG_ENV_HANDLING`` completely
or, starting with v2025.10.0, using the security policy support for runtime
access control.

Zynq 7000
---------

The MMC controller numbering is now fixed: ``mmc0`` & ``mmc1`` for
``&sdhci0`` and ``&sdhci1`` respectively.

Release v2025.03.0
==================

OMAP console fixup
------------------

The option ``CONFIG_DRIVER_SERIAL_NS16550_OMAP_TTYS`` now controls whether
barebox fixes up ``ttyS`` or ``ttyO`` into the kernel command line
``console=`` option.

fixed-partitions on SD/MMC
--------------------------

Linux v6.13-rc1 added ``CONFIG_OF_PARTITION``, which interprets
``fixed-partitions`` nodes in SD/MMC nodes differently to the barebox
behavior: It ignores the GPT/MBR if fixed-partitions are specified,
instead of allowing them to co-exist like in barebox.

To accommodate both the existing barebox and the new kernel functionality,
users should replace ``fixed-partitions``-compatible device tree subnodes
of SD/eMMC with ``barebox,fixed-partitions``.

Similarly, the default for
:ref:`global.of_partition_binding <magicvar_global_of_partition_binding>`
has been changed to the new ``adaptive`` option, which fixes up
``barebox,fixed-partitions`` except for MTD.

Release v2025.05.0
==================

Configuration options
---------------------

  This can be customized via setting the
  :ref:`global.linux.rootwait <magicvar_global_linux_rootwait>`
  variable or by disabling the option.

Bootloader Specification
------------------------

  Previously only the first partition with the XBOOTLDR partition type
  was considered.

  If an XBOOTLDR partition exists, barebox will no longer walk
  all partitions to find further
  bootloader spec entries.

Board support
-------------

  Users should migrate to FIP images with barebox as nontrusted firmware
  (BL33) and the barebox device tree as hardware config.

  Use of multiple device trees is not supported directly by the FIP format
  and can be substituted by a barebox image embedding multiple device trees
  and using the hardware config FIP slot only as dummy.
  See the lxa-tac board for an example.

Shell and magic variables
-------------------------

  This does not affect users setting ``nv boot.default``, but for
  others, barebox will look for bootloader spec on the bootsource
  medium first.

Build system
------------

Bisectability
-------------

Following regressions had a wider impact and could falsify git bisect results:

Release v2025.08.0
==================

W^X on ARM
----------

``CONFIG_ARM_MMU_PERMISSIONS=y`` is now the default and instructs barebox to map
its memory regions with more restricted permissions: Data is no longer
executable
and code as well as read-only data is no longer writable.

This can lead to breakage in code that had invalid assumptions beforehand,
e.g. code expecting on-chip SRAMs to be executable or bogus code casting away
const. Please report to upstream any issues that are resolved by disabling
``CONFIG_ARM_MMU_PERMISSIONS``, so they can be properly fixed.

Bootchooser
-----------

Bootchooser now interprets a top-level ``attempts_locked`` variable.
For more information, see :ref:`attempts lock feature
<bootchooser,attempts_lock>`.

Board support
-------------

The hardcoded Vexpress partition layout for barebox, its environment and state
has been changed. The first 5M of the NOR flash should now be reserved for
barebox use. barebox will, by default, fix up the new partition layout into
the kernel device tree.

Release v2025.09

[Changelog truncated as it exceeds 5000 characters;
the full changelog can be found in an attachment to the AUH email]
---
 meta/recipes-bsp/barebox/barebox-common.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)