diff options
author | Miao Yan <miao.yan@windriver.com> | 2013-11-28 09:51:40 (GMT) |
---|---|---|
committer | Tom Rini <trini@ti.com> | 2013-12-16 13:59:42 (GMT) |
commit | 82450b9a62f381ed3ef40ef3753dd4bda61db90e (patch) | |
tree | ff76c2c08ea1ccfc0b76bd0fc30f8b74492ace77 | |
parent | 35940de1a6648c5adbb89d8f64ba9513bae5e063 (diff) | |
download | u-boot-fsl-qoriq-82450b9a62f381ed3ef40ef3753dd4bda61db90e.tar.xz |
README.vxworks: add a document describing the new VxWorks boot interface
Signed-off-by: Miao Yan <miao.yan@windriver.com>
-rw-r--r-- | doc/README.vxworks | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/README.vxworks b/doc/README.vxworks new file mode 100644 index 0000000..4cb302e --- /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. |