<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools, branch v2024.07-rc1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools?h=v2024.07-rc1</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools?h=v2024.07-rc1'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2024-04-17T23:06:01Z</updated>
<entry>
<title>tools: copyfile: use 64k instead of 512 buffer</title>
<updated>2024-04-17T23:06:01Z</updated>
<author>
<name>Ahelenia Ziemiańska</name>
<email>nabijaczleweli@nabijaczleweli.xyz</email>
</author>
<published>2024-04-09T12:14:34Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7c665e151246cf8b5072ca4f1916f8ed0fa8565c'/>
<id>urn:sha1:7c665e151246cf8b5072ca4f1916f8ed0fa8565c</id>
<content type='text'>
This is a trivial but significant optimization:
mkimage took &gt;200ms (and 49489 writes (of which 49456 512)),
now it takes  110ms (and   419 writes (of which   386 64k)).

sendfile is much more appropriate for this and is done in one syscall,
but doesn't bring any significant speedups over 64k r/w
at the 13M size ranges, so there's no need to introduce
	#if __linux__
	while((size = sendfile(fd_dst, fd_src, NULL, 128 * 1024 * 1024)) &gt; 0)
		;
	if(size != -1) {
		ret = 0;
		goto out;
	}
	#endif

Also extract the buffer size to a macro.

Signed-off-by: Ahelenia Ziemiańska &lt;nabijaczleweli@nabijaczleweli.xyz&gt;
Reviewed-by: Dragan Simic &lt;dsimic@manjaro.org&gt;
</content>
</entry>
<entry>
<title>image-host: Fix error value paths and emit error messages to stderr.</title>
<updated>2024-04-12T14:53:31Z</updated>
<author>
<name>Hugo Cornelis</name>
<email>hugo.cornelis@essensium.com</email>
</author>
<published>2024-03-21T11:22:22Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=55a7d60f8f10b1c3c5a8e29571c065d61f5dd12f'/>
<id>urn:sha1:55a7d60f8f10b1c3c5a8e29571c065d61f5dd12f</id>
<content type='text'>
A recent refactoring in image-host.c messed up the return values of
the function that reads the encryptiong keys.  This patch fixes this
and also makes sure that error output goes to stderr instead of to
stdout.

Signed-off-by: Hugo Cornelis &lt;hugo.cornelis@essensium.com&gt;
</content>
</entry>
<entry>
<title>tools: binman: ti_board_cfg: improve error message</title>
<updated>2024-04-11T21:51:33Z</updated>
<author>
<name>Michael Walle</name>
<email>mwalle@kernel.org</email>
</author>
<published>2024-03-26T09:39:34Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a26bef219bf56363fa00c355029c04c5d6898697'/>
<id>urn:sha1:a26bef219bf56363fa00c355029c04c5d6898697</id>
<content type='text'>
When there is a lint error the user gets the following cryptic message:

  binman: Node '/path/to/some/node': Yamllint error: 18: comments

This isn't very helpful. Improve the message to tell the user that the
number is actually a line number and also tell the user in which file
they have to look.

Signed-off-by: Michael Walle &lt;mwalle@kernel.org&gt;
Reviewed-by: Neha Malcom Francis &lt;n-francis@ti.com&gt;
</content>
</entry>
<entry>
<title>binman: ti-secure: Enable debug extension for combined boot</title>
<updated>2024-04-11T21:51:11Z</updated>
<author>
<name>Manorit Chawdhry</name>
<email>m-chawdhry@ti.com</email>
</author>
<published>2024-03-26T08:07:06Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fbfd2baf975f4a0d6345e4d0ed6094c549fe1d03'/>
<id>urn:sha1:fbfd2baf975f4a0d6345e4d0ed6094c549fe1d03</id>
<content type='text'>
To debug using jtag, ROM needs to unlock jtag debugging on HS devices
and it does that looking at this debug extension.

Add the debug extension and enable it by default.

Link: https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/security/sec_cert_format.html?highlight=debug#sysfw-debug-ext
Signed-off-by: Manorit Chawdhry &lt;m-chawdhry@ti.com&gt;
Reviewed-by: Neha Malcom Francis &lt;n-francis@ti.com&gt;
</content>
</entry>
<entry>
<title>trace: use dynamic string buffer in make_flamegraph()</title>
<updated>2024-04-10T15:34:53Z</updated>
<author>
<name>Vincent Stehlé</name>
<email>vincent.stehle@arm.com</email>
</author>
<published>2024-04-02T11:29:16Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=b782be47f12b1957c67e612e7d3b0ef7b3f32b36'/>
<id>urn:sha1:b782be47f12b1957c67e612e7d3b0ef7b3f32b36</id>
<content type='text'>
The str[] buffer declared in make_flamegraph() is used to hold strings
representing the full call-stacks recorded in traces. The size of this
buffer is currently 500 characters and this works well for the documented
examples.

However, it is possible to exhaust this buffer when processing traces
captured when running the UEFI shell on aarch64 sandbox for example.
Indeed, the maximum length needed for such traces can reach 780 characters.

As it is difficult to evaluate the maximum size that would ever be needed
for all the possible traces, let's use a dynamically allocated `abuf'
instead, which we reallocate when needed.

This fixes the following error:

  String too short (500 chars)

While at it, fix a few typos in strings and comments.

Signed-off-by: Vincent Stehlé &lt;vincent.stehle@arm.com&gt;
Cc: Tom Rini &lt;trini@konsulko.com&gt;
Cc: Simon Glass &lt;sjg@chromium.org&gt;
Cc: Michal Simek &lt;michal.simek@amd.com&gt;
</content>
</entry>
<entry>
<title>tools: open FIT image read-only</title>
<updated>2024-04-10T15:34:53Z</updated>
<author>
<name>Ahelenia Ziemiańska</name>
<email>nabijaczleweli@nabijaczleweli.xyz</email>
</author>
<published>2024-03-21T18:31:54Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=32bc256ced33678d63147acb796aa1cbcc942baf'/>
<id>urn:sha1:32bc256ced33678d63147acb796aa1cbcc942baf</id>
<content type='text'>
Open for reading as O_RDONLY instead of O_RDWR:
the only usage of the fd is for the single read() below;
this prevented
	mkimage -f auto -A arm64 \
		-T kernel -C lz4 -d Image-6.6.15.lz4 \
		-b mt8173-elm-hana-6.6.15.dtb outf
when the inputs were unwritable.

Link: https://bugs.debian.org/1063097
Signed-off-by: Ahelenia Ziemiańska &lt;nabijaczleweli@nabijaczleweli.xyz&gt;
Reviewed-by: Dragan Simic &lt;dsimic@manjaro.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'v2024.04-rc5' into next</title>
<updated>2024-03-26T02:15:47Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2024-03-26T02:15:47Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ab8d9ca3044acf51d8ff3bf3c4718c48f30ad606'/>
<id>urn:sha1:ab8d9ca3044acf51d8ff3bf3c4718c48f30ad606</id>
<content type='text'>
Prepare v2024.04-rc5
</content>
</entry>
<entry>
<title>patman: Properly document the patchwork_url setting</title>
<updated>2024-03-21T06:36:54Z</updated>
<author>
<name>Douglas Anderson</name>
<email>dianders@chromium.org</email>
</author>
<published>2024-03-11T21:02:45Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fcd0c8b8474f7db0b94608424715a73fbeba92dc'/>
<id>urn:sha1:fcd0c8b8474f7db0b94608424715a73fbeba92dc</id>
<content type='text'>
The "Series-patchwork-url:" tag description says that it overrides the
settings file but doesn't specify the name of the setting. Elsewhere
in the documentation about the "useful" settings we see a setting that
sounds promising called "patchwork_server" that's actually not a valid
setting. It should be "patchwork_url".

Fix these problems so the doc is right and more useful.

Signed-off-by: Douglas Anderson &lt;dianders@chromium.org&gt;
</content>
</entry>
<entry>
<title>CI: Move to latest container image</title>
<updated>2024-03-15T12:18:54Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2024-03-15T02:36:43Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=cacc0b2678c03d694e8be70f8e7b7601825f1c0f'/>
<id>urn:sha1:cacc0b2678c03d694e8be70f8e7b7601825f1c0f</id>
<content type='text'>
This moves us to our latest container image, which is now based on the
current "Jammy" tag.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>CI: Cherry-pick reset support for m68k for QEMU</title>
<updated>2024-03-14T20:11:42Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2024-03-11T14:02:43Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=074bfab54d83ab1da3e872d363570bba9e134f62'/>
<id>urn:sha1:074bfab54d83ab1da3e872d363570bba9e134f62</id>
<content type='text'>
In order to support the reset pytest on QEMU on m68k platforms we need
to grab this change from upstream.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
</feed>
