[Xen-devel] [PATCH] docs/arm64: update the documention for loading XSM support

[fu.wei@xxxxxxxxxx]

From: Fu Wei <fu.wei@xxxxxxxxxx>

This patch updates the documention for loading XSM by the module which
lacks a specific compatible string. This mechanism has been added by the
commit ca32012341f3de7d3975407fb963e6028f0d0c8b

Signed-off-by: Fu Wei <fu.wei@xxxxxxxxxx>
---
 docs/misc/arm/device-tree/booting.txt | 17 +++++++++++++----
 1 file changed, 13 insertions(+), 4 deletions(-)

diff --git a/docs/misc/arm/device-tree/booting.txt 
b/docs/misc/arm/device-tree/booting.txt
index ad98bf3..f45a9c4 100644
--- a/docs/misc/arm/device-tree/booting.txt
+++ b/docs/misc/arm/device-tree/booting.txt
@@ -24,10 +24,19 @@ Each node contains the following properties:
        string (which must always be present).
 
        Xen will assume that the first module which lacks a more
-       specific compatible string is a "multiboot,kernel" and that
-       the second such is a "multiboot,ramdisk". Any subsequent
-       modules which lack a specific compatiblity string will not
-       receive any special treatment.
+       specific compatible string is a "multiboot,kernel". Xen will
+       detect the XSM magic from the second module which lacks of
+       a specific compatiblity string:
+       - if it's XSM, Xen will assume that the second such is a
+       "xen,xsm-policy". and also assume user won't load ramdisk;
+       - if it's not XSM, Xen will assume that the second such is a
+       "multiboot,ramdisk".
+       So if user want to load ramdisk without a specific compatiblity,
+       it must be the 2nd one.
+       Xen will also detect the XSM Magic for the following modules
+       which lack of a specific compatiblity, and assume that the module
+       is a "xen,xsm-policy" or "multiboot,module", according to the
+       result of detection.
 
        Xen 4.4 supported a different set of legacy compatible strings
        which remain supported such that systems supporting both 4.4
-- 
2.5.5


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel