blob: 4cb302e7f4face2e70f2186a9b74c8932725dd5f [file] [log] [blame]
Miao Yan82450b92013-11-28 17:51:40 +08001From VxWorks 6.9+ (not include 6.9), VxWorks starts adopting device tree as its hardware
2decription mechansim (for PowerPC and ARM), thus requiring boot interface changes.
3This section will describe the new interface.
4
5For PowerPC, the calling convention of the new VxWorks entry point conforms to the ePAPR standard,
6which is shown below (see ePAPR for more details):
7
8 void (*kernel_entry)(fdt_addr,
9 0, 0, EPAPR_MAGIC, boot_IMA, 0, 0)
10
11For ARM, the calling convention is show below:
12
13 void (*kernel_entry)(void *fdt_addr)
14
15When booting new VxWorks kernel (uImage format), the parameters passed to bootm is like below:
16
17 bootm <kernel image address> - <device tree address>
18
19The do_bootvx command still works as it was for older VxWorks kernels.