aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2013-04-25 14:27:57 +0200
committerRob Herring <rob.herring@calxeda.com>2013-04-25 15:05:09 -0500
commita2b9ea73967386ec5e524ab206bd549d5aafea17 (patch)
treea1771e4ba8e83171f9f258ec2ff0247193aab160
parenta2f682aeeecfa791de19de63509566d156d0d1a3 (diff)
Documentation/devicetree: make semantic of initrd-end more explicit
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
-rw-r--r--Documentation/devicetree/usage-model.txt8
1 files changed, 5 insertions, 3 deletions
diff --git a/Documentation/devicetree/usage-model.txt b/Documentation/devicetree/usage-model.txt
index ef9d06c9f8fd..0efedaad5165 100644
--- a/Documentation/devicetree/usage-model.txt
+++ b/Documentation/devicetree/usage-model.txt
@@ -191,9 +191,11 @@ Linux it will look something like this:
};
The bootargs property contains the kernel arguments, and the initrd-*
-properties define the address and size of an initrd blob. The
-chosen node may also optionally contain an arbitrary number of
-additional properties for platform-specific configuration data.
+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.
During early boot, the architecture setup code calls of_scan_flat_dt()
several times with different helper callbacks to parse device tree

Privacy Policy