Signed-off-by: Samuel Dionne-Riel <samuel@xxxxxxxxxxxxxxx>
---
This issue was noticed while following the documentation when
implementing initrd support in a platform-specific bootloader.
It wouldn't work, even though the documentation was followed as written.
One can verify that there are no references of prefix-less /chosen
initrd-* properties in the whole codebase using these commands:
$ grep -R 'initrd-\(start\|end\)' | grep -v 'linux,initrd-\(start\|end\)'
Documentation/devicetree/usage-model.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/usage-model.rst b/Documentation/devicetree/usage-model.rst
index b6a287955ee56..39d023cc69a8a 100644
--- a/Documentation/devicetree/usage-model.rst
+++ b/Documentation/devicetree/usage-model.rst
@@ -192,16 +192,16 @@ Linux it will look something like this::
chosen {
bootargs = "console=ttyS0,115200 loglevel=8";
- initrd-start = <0xc8000000>;
- initrd-end = <0xc8200000>;
+ linux,initrd-start = <0xc8000000>;
+ linux,initrd-end = <0xc8200000>;
};
The bootargs property contains the kernel arguments, and the initrd-*
properties define the address and size of an initrd blob. Note that
-initrd-end is the first address after the initrd image, so this doesn't
-match the usual semantic of struct resource. The chosen node may also
-optionally contain an arbitrary number of additional properties for
-platform-specific configuration data.
+linux,initrd-end is the first address after the initrd image, so this
+doesn't match the usual semantic of struct resource. The chosen node
+may also optionally contain an arbitrary number of additional
+properties for platform-specific configuration data.
During early boot, the architecture setup code calls of_scan_flat_dt()
several times with different helper callbacks to parse device tree
--
2.32.0
--
Samuel Dionne-Riel
