<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/doc/develop/driver-model, branch main</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/doc/develop/driver-model?h=main</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/doc/develop/driver-model?h=main'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2026-08-29T04:41:36Z</updated>
<entry>
<title>doc: switch to HTTPS for a few links</title>
<updated>2026-08-29T04:41:36Z</updated>
<author>
<name>Quentin Schulz</name>
<email>quentin.schulz@cherry.de</email>
</author>
<published>2026-08-27T19:53:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c60dee22fcb0a7724d11521ba6435cd16c8f7f10'/>
<id>urn:sha1:c60dee22fcb0a7724d11521ba6435cd16c8f7f10</id>
<content type='text'>
It's 2026, we really should be using HTTPS wherever possible. The links
in this commit were individually tested, they work fine (the sipeed one
sometimes times out but I'm guessing it's hosted in China and it's not
uncommon for Europeans to have issues reaching servers there).

Signed-off-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
</content>
</entry>
<entry>
<title>doc: develop/driver-model: fs_firmware_loader: update link</title>
<updated>2026-08-29T04:41:35Z</updated>
<author>
<name>Quentin Schulz</name>
<email>quentin.schulz@cherry.de</email>
</author>
<published>2026-08-27T19:52:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=d8c262c673964f4050e0818439d05c210f7abe21'/>
<id>urn:sha1:d8c262c673964f4050e0818439d05c210f7abe21</id>
<content type='text'>
The current link redirects to a generic page on the Intel website.
Looking at the Wayback Machine[1], it really looks like what is
currently exposed in the official kernel docs, so used that instead.

[1] https://web.archive.org/web/20220916014111/https://01.org/linuxgraphics/gfx-docs/drm/driver-api/firmware/index.html

Signed-off-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
</content>
</entry>
<entry>
<title>rockchip: pinctrl: replace RK_FUNC_n defines</title>
<updated>2026-07-23T13:00:08Z</updated>
<author>
<name>Johan Jonker</name>
<email>jbx6244@gmail.com</email>
</author>
<published>2026-06-09T20:22:58Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e504d9cffbafbd4dd267ab9a73bf1ee58d89e8e1'/>
<id>urn:sha1:e504d9cffbafbd4dd267ab9a73bf1ee58d89e8e1</id>
<content type='text'>
The use of RK_FUNC_n defines is deprecated in the upstream
rockchip.h file. Replace all them by the function number.

Signed-off-by: Johan Jonker &lt;jbx6244@gmail.com&gt;
Reviewed-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
Link: https://patch.msgid.link/51cb65e5-1702-467f-b961-c9cdd029056f@gmail.com
Signed-off-by: Quentin Schulz &lt;u-boot@0leil.net&gt;
</content>
</entry>
<entry>
<title>doc: Remove the patman documentation</title>
<updated>2026-07-06T14:28:50Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2026-07-05T19:32:13Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f6c56009f6600ad87336484d258849d2bf36d010'/>
<id>urn:sha1:f6c56009f6600ad87336484d258849d2bf36d010</id>
<content type='text'>
The full patman manual now lives with the standalone patch-manager
package, making the 1000-line copy in the tree redundant.

Remove the in-tree manual, its README and the doc/develop/patman.rst
toctree page.

The sending-patches guide already introduces patman, so point it at the
patch-manager package instead of the now-dead ':doc:' cross-reference
and, with the manual gone, add a couple of lines on how the tool works.
Point the SPI howto at that guide too, rather than repeating the install
details.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Mattijs Korpershoek &lt;mkorpershoek@kernel.org&gt;
</content>
</entry>
<entry>
<title>doc: develop: virtio: Fix qemu example (true/false -&gt; on/off)</title>
<updated>2025-10-26T15:03:35Z</updated>
<author>
<name>Wolfgang Wallner</name>
<email>wolfgang.wallner@br-automation.com</email>
</author>
<published>2025-10-24T15:12:05Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1f6da608c3d9a9a7d189177614cfb8d6a1ad8d6c'/>
<id>urn:sha1:1f6da608c3d9a9a7d189177614cfb8d6a1ad8d6c</id>
<content type='text'>
The given qemu examples use true/false, while qemu actually on/off.

Signed-off-by: Wolfgang Wallner &lt;wolfgang.wallner@br-automation.com&gt;
</content>
</entry>
<entry>
<title>doc: Fix typos</title>
<updated>2025-10-26T15:03:27Z</updated>
<author>
<name>Wolfgang Wallner</name>
<email>wolfgang.wallner@br-automation.com</email>
</author>
<published>2025-10-24T15:11:59Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ed00d12c015aec7c316fcd482737181f9dff8f4d'/>
<id>urn:sha1:ed00d12c015aec7c316fcd482737181f9dff8f4d</id>
<content type='text'>
Fix typos/wording in various files in doc/.

Signed-off-by: Wolfgang Wallner &lt;wolfgang.wallner@br-automation.com&gt;
Reviewed-by: E Shattow &lt;e@freeshell.de&gt;
</content>
</entry>
<entry>
<title>doc: Update mentions of README.fdt-control</title>
<updated>2025-09-27T07:20:22Z</updated>
<author>
<name>E Shattow</name>
<email>e@freeshell.de</email>
</author>
<published>2025-09-23T22:30:50Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c9aad6dbd97b44fccaf761a1f07932ae567d76b7'/>
<id>urn:sha1:c9aad6dbd97b44fccaf761a1f07932ae567d76b7</id>
<content type='text'>
Update documents 'README.fdt-control' reference to replacement 'control.rst':
  doc/arch/nios2.rst
  dts/Makefile

Also convert some adjacent pathname mentions to rST links where applicable

Fixes: 3e9fddfc4f14 "doc: Move devicetree control doc to rST"
Signed-off-by: E Shattow &lt;e@freeshell.de&gt;
</content>
</entry>
<entry>
<title>dm: doc: Fix example</title>
<updated>2025-04-11T01:32:55Z</updated>
<author>
<name>Miquel Raynal</name>
<email>miquel.raynal@bootlin.com</email>
</author>
<published>2025-04-03T07:39:02Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9fe367bb60d377402617bb818796bff59e82e7c6'/>
<id>urn:sha1:9fe367bb60d377402617bb818796bff59e82e7c6</id>
<content type='text'>
`.priv_data_size` does not exist. I believe the actual structure member
was supposed to be `.priv_auto`.

Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Miquel Raynal &lt;miquel.raynal@bootlin.com&gt;
</content>
</entry>
<entry>
<title>dm: clarify DM_FLAG_PROBE_AFTER_BIND behaviour</title>
<updated>2025-03-30T15:09:04Z</updated>
<author>
<name>Caleb Connolly</name>
<email>caleb.connolly@linaro.org</email>
</author>
<published>2025-01-17T07:28:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8a0e6212bb5ef547712e922a41555eb7d1aee1ab'/>
<id>urn:sha1:8a0e6212bb5ef547712e922a41555eb7d1aee1ab</id>
<content type='text'>
The DM_FLAG_PROBE_AFTER_BIND flag only makes sense on a per-device
basis, however recently added documentation as well as some confused
drivers imply that it might be added to a driver definition, this does
nothing.

Clarify the new documentation and expand on the comment by the
definition to point people in the right direction.

Signed-off-by: Caleb Connolly &lt;caleb.connolly@linaro.org&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Acked-by: Michal Simek &lt;michal.simek@amd.com&gt;
</content>
</entry>
<entry>
<title>common: Move autoprobe out to board init</title>
<updated>2025-01-14T17:42:51Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-11-20T15:36:41Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=6995f2c8be901b5f3f4183ccc4a58c209e8bce52'/>
<id>urn:sha1:6995f2c8be901b5f3f4183ccc4a58c209e8bce52</id>
<content type='text'>
Rather than doing autoprobe within the driver model code, move it out to
the board-init code. This makes it clear that it is a separate step from
binding devices.

For now this is always done twice, before and after relocation, but we
should discuss whether it might be possible to drop the post-relocation
probe.

For boards with SPL, the autoprobe is still done there as well.

Note that with this change, autoprobe happens after the
EVT_DM_POST_INIT_R/F events are sent, rather than before.

Link: https://lore.kernel.org/u-boot/20240626235717.272219-1-marex@denx.de/

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