From: anonymix007 <48598263+anonymix007@users.noreply.github.com>
Date: Tue, 22 Oct 2024 12:07:15 +0000 (+0300)
Subject: man: Document stub behaviour for .hwids and .dtbauto sections
X-Git-Tag: v257-rc1~19^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F34855%2Fhead;p=thirdparty%2Fsystemd.git
man: Document stub behaviour for .hwids and .dtbauto sections
---
diff --git a/man/systemd-stub.xml b/man/systemd-stub.xml
index 439d999c64c..6625fca91ef 100644
--- a/man/systemd-stub.xml
+++ b/man/systemd-stub.xml
@@ -79,6 +79,20 @@
A .dtb section with a compiled binary DeviceTree.
+ Zero or more .dtbauto sections. Stub will always try to find first matching one.
+ Matching process extracts first compatible string from .dtbauto
+ section and compares it with the first Devicetree's compatible string supplied by
+ the firmware in configuration tables. If firmware does not provide Devicetree, matching with
+ .hwids section will be used instead. Stub will use SMBIOS data to calculate hardware
+ IDs of the machine (as per specification),
+ then it will proceed to trying to find any of them in .hwids section and will use first
+ matching entry's compatible as a search key among the .dtbauto
+ entries, in a similar fashion as the use of compatible string read from the firmware
+ provided Devicetree was described before. First matching .dtbauto section will be
+ loaded and will override .dtb if present.
+
+ A .hwids section with hardware IDs of the machines to match Devicetrees (refer to .dtbauto section description).
+
A .uname section with the kernel version information, i.e. the
output of uname -r for the kernel included in the .linux
section.