u-boot.git/tools, branch v2026.01-rc2

dm: Remove pre-schema tag support

2025-11-10T17:30:56+00:00

Support for using "u-boot,dm-..." rather than "bootph-..." has been
deprecated since February 2023. Any platforms using this have had a
console message saying to migrate by 2023.07. Go and remove all support
here now, for the v2026.01 release.

The results of this change that aren't clear from the above are that we
still have a checkpatch.pl error message, and document in
doc/develop/spl.rst that they have been migrated since 2023. We also
change the key2dtsi.py tool to use the correct bootph phase rather than
the legacy phase.

Signed-off-by: Tom Rini

tools: key2dtsi: Write out modulus and r-squared with the correct length

2025-11-06T14:31:25+00:00

Align the implementation to rsa_add_verify_data() by writing the modulus
and r-squared properties with the same length as the key itself. This
fixes signature verification issues when one of the parameters has
leading zeros.

Reported-by: Hans Gfirtner (Nokia) 
Signed-off-by: Jan Kiszka

CI: Move to Ubuntu 'Jammy' 20251001 tag

2025-11-04T17:33:41+00:00

This also incorporates the following commits to the Dockerfile:
da7942de29f7 Dockerfile: remove Python 2.7
183299d9a400 docker: add OP-TEE and TF-A build for testing Firmware Handoff

Signed-off-by: Tom Rini

Dockerfile: remove Python 2.7

2025-11-04T17:01:54+00:00

We don't use Python 2 anywhere. Remove the package from our Docker image.

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Simon Glass

Merge patch series "Enable Firmware Handoff CI test on qemu_arm64"

2025-11-04T16:59:50+00:00

Raymond Mao  says:

This patch series enable Firmware Handoff [1] CI tests on qemu_arm64 by:
1. fetch MbedTLS (v3.6), OP-TEE (v4.7.0) and TF-A (v2.13.0);
2. build bl1 and fip with both Firmware Handoff and Measured Boot
   enabled;
3. pytest to validate the Firmware Handoff feature via bloblist by
   checking the existence of expected FDT nodes and TPM events generated
   and handed over from TF-A/OP-TEE.

[1] https://github.com/FirmwareHandoff/firmware_handoff

Link: https://lore.kernel.org/r/20251021181703.598342-1-raymond.mao@linaro.org

docker: add OP-TEE and TF-A build for testing Firmware Handoff

2025-11-04T16:59:41+00:00

Fetch OP-TEE (4.7.0), TF-A (v2.13.0), MbedTLS (v3.6) and build
bl1 and fip with both Firmware Handoff and Measured Boot enabled.

Signed-off-by: Raymond Mao 
Acked-by: Jerome Forissier

binman: btool: mkimage: fix Bintoolmkimage.run() method docstring

2025-11-02T18:15:23+00:00

Commit 65e2c14d5a5a ("binman: btool: mkimage: use Bintool.version")
removed the version argument from the run method but forgot to remove it
from the method docstring, so let's fix this oversight.

Fixes: 65e2c14d5a5a ("binman: btool: mkimage: use Bintool.version")
Signed-off-by: Quentin Schulz 
Reviewed-by: Simon Glass 
Reviewed-by: Kever Yang

doc: develop: Change formatting to make binman doc more readable

2025-10-26T15:03:26+00:00

Change the formatting of binman.rst so that the compiled HTML output
becomes more readable. Changes include enumerations and the escaping of
arguments starting with a double dash (e.g. --debug).

Reviewed-by: Simon Glass 
Signed-off-by: Wolfgang Wallner

doc: develop: Fix typos in binman/binman.rst

2025-10-26T14:40:54+00:00

Fix some typos in binman.rst.

Reviewed-by: Simon Glass 
Signed-off-by: Wolfgang Wallner

mkimage: fit: erase data-size property when importing data

2025-10-10T19:28:36+00:00

When importing data, the data-offset property is removed and the data
content is imported inside the data property of the node.

When mkimage is run twice on the same FIT, data-size property is already
set in the second run, from the first run (via the fit_export_data
function). If we don't remove the data-size property, nothing guarantees
it matches the actual size of data within the data property. To avoid
possible mistakes when handling the data property, let's simply remove
the data-size property as well.

This also fixes an ordering issue of the data-size and data-offset
properties in FIT when comparing the FIT after one run of mkimage and a
second run. This is due to fit_export_data setting data-offset property
first (it doesn't exist so it's added) and then data-size (it doesn't
exist so it's added) for the first run, while it sets data-offset
property first (removed in fit_import_data, so it doesn't exist so it's
added) and then data-size (it exists already from the first run, so it's
simply modified) for the second run.

Signed-off-by: Quentin Schulz