1*82450b9aSMiao YanFrom VxWorks 6.9+ (not include 6.9), VxWorks starts adopting device tree as its hardware 2*82450b9aSMiao Yandecription mechansim (for PowerPC and ARM), thus requiring boot interface changes. 3*82450b9aSMiao YanThis section will describe the new interface. 4*82450b9aSMiao Yan 5*82450b9aSMiao YanFor PowerPC, the calling convention of the new VxWorks entry point conforms to the ePAPR standard, 6*82450b9aSMiao Yanwhich is shown below (see ePAPR for more details): 7*82450b9aSMiao Yan 8*82450b9aSMiao Yan void (*kernel_entry)(fdt_addr, 9*82450b9aSMiao Yan 0, 0, EPAPR_MAGIC, boot_IMA, 0, 0) 10*82450b9aSMiao Yan 11*82450b9aSMiao YanFor ARM, the calling convention is show below: 12*82450b9aSMiao Yan 13*82450b9aSMiao Yan void (*kernel_entry)(void *fdt_addr) 14*82450b9aSMiao Yan 15*82450b9aSMiao YanWhen booting new VxWorks kernel (uImage format), the parameters passed to bootm is like below: 16*82450b9aSMiao Yan 17*82450b9aSMiao Yan bootm <kernel image address> - <device tree address> 18*82450b9aSMiao Yan 19*82450b9aSMiao YanThe do_bootvx command still works as it was for older VxWorks kernels. 20