From: Miao Yan <miao.yan@windriver.com>
Date: Thu, 28 Nov 2013 09:51:40 +0000 (+0800)
Subject: README.vxworks: add a document describing the new VxWorks boot interface
X-Git-Url: http://git.dujemihanovic.xyz/login.html?a=commitdiff_plain;h=82450b9a62f381ed3ef40ef3753dd4bda61db90e;p=u-boot.git

README.vxworks: add a document describing the new VxWorks boot interface

Signed-off-by: Miao Yan <miao.yan@windriver.com>
---

diff --git a/doc/README.vxworks b/doc/README.vxworks
new file mode 100644
index 0000000000..4cb302e7f4
--- /dev/null
+++ b/doc/README.vxworks
@@ -0,0 +1,19 @@
+From VxWorks 6.9+ (not include 6.9), VxWorks starts adopting device tree as its hardware
+decription mechansim (for PowerPC and ARM), thus requiring boot interface changes.
+This section will describe the new interface.
+
+For PowerPC, the calling convention of the new VxWorks entry point conforms to the ePAPR standard,
+which is shown below (see ePAPR for more details):
+
+    void (*kernel_entry)(fdt_addr,
+              0, 0, EPAPR_MAGIC, boot_IMA, 0, 0)
+
+For ARM, the calling convention is show below:
+
+    void (*kernel_entry)(void *fdt_addr)
+
+When booting new VxWorks kernel (uImage format), the parameters passed to bootm is like below:
+
+    bootm <kernel image address> - <device tree address>
+
+The do_bootvx command still works as it was for older VxWorks kernels.