Merge tag 'v2026.04-rc4' into next

Prepare v2026.04-rc4

4 files changed, 21 insertions, 47 deletions

diff --git a/doc/board/samsung/exynos-mobile.rst b/doc/board/samsung/exynos-mobile.rst
index 37718af1fea..d0173b1f8cb 100644
--- a/doc/board/samsung/exynos-mobile.rst
+++ b/doc/board/samsung/exynos-mobile.rst
@@ -25,12 +25,13 @@ If a cross-compiler is required, install it and set it up like so:
 
 	export CROSS_COMPILE=aarch64-linux-gnu-
 
-Then, run the following commands to build U-Boot:
+Then, run the following commands to build U-Boot (replace ``<dtb>`` with the
+upstream DTB path for the target device):
 
 .. prompt:: bash $
 
 	make O=.output exynos-mobile_defconfig
-	make O=.output -j$(nproc)
+	make DEVICE_TREE=<dtb> O=.output -j$(nproc)
 
 If successful, the U-Boot binary will be present in ``.output/u-boot.bin``.
 
diff --git a/doc/board/samsung/exynos-mobile/exynos7870.rst b/doc/board/samsung/exynos-mobile/exynos7870.rst
index bbd857580b8..702b21244eb 100644
--- a/doc/board/samsung/exynos-mobile/exynos7870.rst
+++ b/doc/board/samsung/exynos-mobile/exynos7870.rst
@@ -6,54 +6,20 @@ Samsung Exynos 7870 Boards
 
 Preparation
 -----------
-Create the following device tree (named ``stub.dts``)
 
-.. code-block:: devicetree
-
-	/dts-v1/;
-
-	/ {
-		compatible = "samsung,exynos7870";
-		#address-cells = <2>;
-		#size-cells = <1>;
-
-		model_info-chip = <7870>;
-		model_info-hw_rev = <0>;
-		model_info-hw_rev_end = <255>;
-
-		chosen {
-		};
-
-		memory@80000000 {
-			device_type = "memory";
-			reg = <0x0 0x80000000 0x0>;
-		};
-
-		memory@100000000 {
-			device_type = "memory";
-			reg = <0x1 0x00000000 0x0>;
-		};
-	};
-
-The chosen node and memory ranges are populated by S-BOOT. A certain device
-model may have multiple variants, with differing amounts of RAM and storage. The
-RAM capacity information is graciously provided by S-BOOT's device tree
-overlays.
-
-Compile it to a device tree blob, then pack it in the QCDT format [1]_ using
-``dtbTool-exynos`` [2]_ by issuing the following commands:
+Pack the device tree blob in the QCDT format [1]_ using ``dtbTool-exynos`` [2]_
+by issuing the following commands:
 
 .. prompt:: bash $
 
-	dtc -I dts -O dtb -o stub.dtb stub.dts
-	dtbTool-exynos -o stub-dt.img stub.dtb
+	dtbTool-exynos -o stub-dt.img .output/u-boot.dtb
 
 Finally, use ``mkbootimg`` by osm0sis [3]_ to generate the boot image:
 
 .. prompt:: bash $
 
 	mkbootimg -o u-boot.img \
-		--kernel	.output/u-boot.bin \
+		--kernel	.output/u-boot-nodtb.bin \
 		--dt		stub-dt.img
 
 Offsets are not provided to ``mkbootimg`` as S-BOOT ignores them.
diff --git a/doc/develop/release_cycle.rst b/doc/develop/release_cycle.rst
index 0544929df84..74834f5bd87 100644
--- a/doc/develop/release_cycle.rst
+++ b/doc/develop/release_cycle.rst
@@ -77,7 +77,7 @@ For the next scheduled release, release candidates were made on:
 
 * U-Boot |next_ver|-rc3 was released on Mon 23 February 2026.
 
-.. * U-Boot |next_ver|-rc4 was released on Mon 09 March 2026.
+* U-Boot |next_ver|-rc4 was released on Mon 09 March 2026.
 
 .. * U-Boot |next_ver|-rc5 was released on Mon 23 March 2026.
 
diff --git a/doc/usage/fit/signature.rst b/doc/usage/fit/signature.rst
index e5b5a8432e9..da08cc75c3a 100644
--- a/doc/usage/fit/signature.rst
+++ b/doc/usage/fit/signature.rst
@@ -353,20 +353,27 @@ meantime.
 Details
 -------
 The signature node contains a property ('hashed-nodes') which lists all the
-nodes that the signature was made over.  The image is walked in order and each
-tag processed as follows:
+nodes that the signature was made over.  The signer (mkimage) writes this
+property as a record of what was included in the hash.  During verification,
+however, U-Boot does not read 'hashed-nodes'. Instead it rebuilds the node
+list from the configuration's own image references (kernel, fdt, ramdisk,
+etc.), since 'hashed-nodes' is not itself covered by the signature. The
+rebuilt list always includes the root node, the configuration node, each
+referenced image node and its hash/cipher subnodes.
+
+The image is walked in order and each tag processed as follows:
 
 DTB_BEGIN_NODE
     The tag and the following name are included in the signature
-    if the node or its parent are present in 'hashed-nodes'
+    if the node or its parent are present in the node list
 
 DTB_END_NODE
     The tag is included in the signature if the node or its parent
-    are present in 'hashed-nodes'
+    are present in the node list
 
 DTB_PROPERTY
     The tag, the length word, the offset in the string table, and
-    the data are all included if the current node is present in 'hashed-nodes'
+    the data are all included if the current node is present in the node list
     and the property name is not 'data'.
 
 DTB_END
@@ -374,7 +381,7 @@ DTB_END
 
 DTB_NOP
     The tag is included in the signature if the current node is present
-    in 'hashed-nodes'
+    in the node list
 
 In addition, the signature contains a property 'hashed-strings' which contains
 the offset and length in the string table of the strings that are to be