<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools, branch main</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools?h=main</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools?h=main'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2026-07-14T21:42:08Z</updated>
<entry>
<title>Merge patch series "tools: qconfig: print a proper error when database is missing"</title>
<updated>2026-07-14T21:42:08Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-07-14T21:42:08Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8dbe57ba648648c4897717cebbc4505a8e0a8c23'/>
<id>urn:sha1:8dbe57ba648648c4897717cebbc4505a8e0a8c23</id>
<content type='text'>
Julien Stephan &lt;jstephan@baylibre.com&gt; says:

When I first ran ./tools/qconfig.py, it immediately crashed with a
Python traceback because the configuration database had not yet been
generated.

This series adds a simple pre-check that detects this condition and
prints a clear error message instructing the user to generate the
database first using the -b option, instead of failing with an unhandled
exception.

While looking at the script, I also noticed that the help text still
references the obsolete moveconfig.rst document. This series updates
that reference as well.

Link: https://lore.kernel.org/r/20260702-qconfig-check-for-db-v1-0-f0b96bf8fa44@baylibre.com
</content>
</entry>
<entry>
<title>qconfig: Rename the doc link in help text</title>
<updated>2026-07-14T21:41:23Z</updated>
<author>
<name>Julien Stephan</name>
<email>jstephan@baylibre.com</email>
</author>
<published>2026-07-02T14:04:42Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ab106a8564811b0cdbcec4b2998145dc5b304783'/>
<id>urn:sha1:ab106a8564811b0cdbcec4b2998145dc5b304783</id>
<content type='text'>
This was missed during the renaming of the tool. Fix it.

Signed-off-by: Julien Stephan &lt;jstephan@baylibre.com&gt;
Fixes: ea4d6dead372 ("moveconfig: Rename the tool to qconfig")
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>tools: qconfig: print a proper error when database is missing</title>
<updated>2026-07-14T21:41:23Z</updated>
<author>
<name>Julien Stephan</name>
<email>jstephan@baylibre.com</email>
</author>
<published>2026-07-02T14:04:41Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e24624017f49dfe22845316ccd11b8c4487c2022'/>
<id>urn:sha1:e24624017f49dfe22845316ccd11b8c4487c2022</id>
<content type='text'>
When CONFIG_DATABASE does not exist, read_database() would fail with a
Python traceback. Add a pre-check to print a clear message asking the
user to generate the database first with the -b option.

Signed-off-by: Julien Stephan &lt;jstephan@baylibre.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>tools: binman: ti_board_cfg: Add configurable sw-rev support</title>
<updated>2026-07-13T23:06:33Z</updated>
<author>
<name>Shiva Tripathi</name>
<email>s-tripathi1@ti.com</email>
</author>
<published>2026-06-30T15:28:09Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ab2266aff3622a1cf1a5e76a0702688b2bb538a5'/>
<id>urn:sha1:ab2266aff3622a1cf1a5e76a0702688b2bb538a5</id>
<content type='text'>
The software revision field in the combined board config binary header
was hardcoded to 1, preventing independent control from SBL SWREV
configured via ti-secure-rom's sw-rev property.

Add support for the optional 'sw-rev' DTS property in ti_board_config
nodes, which sets the SWREV byte in the header. Defaults to 1 for
backward compatibility.

Signed-off-by: Shiva Tripathi &lt;s-tripathi1@ti.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: allow zynqmpbif to use a register initialization file</title>
<updated>2026-07-08T06:55:51Z</updated>
<author>
<name>Erich E. Hoover</name>
<email>erich.e.hoover@gmail.com</email>
</author>
<published>2026-06-12T15:04:54Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=cc0d3f546063383b6547ffe850f61818eae8c700'/>
<id>urn:sha1:cc0d3f546063383b6547ffe850f61818eae8c700</id>
<content type='text'>
The ZynqMP Boot Image Format allows specifying the register
initialization file with the "[init]" attribute.  Since this
feature is already supported by the "zynqmpimage" backend, this
commit leverages that existing capability to add support for the
"[init]" attribute in the zynqmpbif backend:
https://docs.amd.com/r/en-US/ug1283-bootgen-user-guide/init

This currently uses the same register initialization file format as
zynqmpimage (ASCII text hex values with each line composed of a pair
of register address and value), for example:
===
0xff003248 0x12345678
===
It is not, yet, compatible with the format used by bootgen:
https://docs.amd.com/r/en-US/ug1283-bootgen-user-guide/Initialization-Pairs-and-INT-File-Attribute

Use this feature, with other zynqmpbif options, like so:
===
image : {
     [init] reginit.int
     [bootloader] fsbl.elf
     [pmufw_image] pmufw.elf
     [destination_cpu=a53-0, exception_level=el-3] bl31.elf
     [destination_cpu=a53-0, exception_level=el-2, load=0x08000000,
startup=0x08000000] u-boot.bin
}
===

Signed-off-by: Erich E. Hoover &lt;erich.e.hoover@gmail.com&gt;
Signed-off-by: Michal Simek &lt;michal.simek@amd.com&gt;
Link: https://lore.kernel.org/r/20260612150454.2194375-1-erich.e.hoover@gmail.com
</content>
</entry>
<entry>
<title>Merge branch 'next'</title>
<updated>2026-07-07T00:26:12Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-07-07T00:26:12Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ee5d46b45ec0c63f8f9dd1e816e0dac3452ccc3d'/>
<id>urn:sha1:ee5d46b45ec0c63f8f9dd1e816e0dac3452ccc3d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>patman: Remove the patch-management code</title>
<updated>2026-07-06T14:28:51Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2026-07-05T19:32:17Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=91b94aff149d2c6efe3afa81adaf5edcc6119221'/>
<id>urn:sha1:91b94aff149d2c6efe3afa81adaf5edcc6119221</id>
<content type='text'>
Delete the command-line tool and its supporting modules, now that this
functionality lives in the standalone patch-manager package.

Keep the modules that buildman still imports (commit and patchstream,
plus their dependencies series, get_maintainer and settings), along with
the stub command. Trim __init__.py to match.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>patman: Remove the test suite</title>
<updated>2026-07-06T14:28:51Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2026-07-05T19:32:16Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f7a4848a9ca37add093628a3f60fb79201eb5fe6'/>
<id>urn:sha1:f7a4848a9ca37add093628a3f60fb79201eb5fe6</id>
<content type='text'>
These tests cover the patch-management functionality, which is being
removed from the tree in favour of the standalone patch-manager package.
Drop the tests and their data files.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>patman: Replace the tool with a stub for patch-manager</title>
<updated>2026-07-06T14:28:51Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2026-07-05T19:32:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f2cf4315339271d48b40628c04c25be24c231a4f'/>
<id>urn:sha1:f2cf4315339271d48b40628c04c25be24c231a4f</id>
<content type='text'>
patman is now maintained as a standalone 'patch-manager' package, rather
than in the U-Boot tree. Replace the command with a small stub which
tells people how to install it.

buildman still uses the shared modules commit and patchstream (and their
dependencies), so leave those in place; the patches that follow remove
the patch-management code itself.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>tools: Stop packaging patman as a pip module</title>
<updated>2026-07-06T14:28:50Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2026-07-05T19:32:21Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c2f2085b1540146fd2a229342366622d1970cd90'/>
<id>urn:sha1:c2f2085b1540146fd2a229342366622d1970cd90</id>
<content type='text'>
patman is no longer shipped from the U-Boot tree, so drop it from the
'make pip' target and from make_pip.sh, and remove its packaging files
(setup.py, pyproject.toml, requirements.txt). Nothing else refers to
them by this point in the series, so they can go.

Also fix binman's pyproject.toml, which declares package-data for a
'patman' package (a copy-paste leftover); use 'binman' instead.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
