upstream u-boot with additional patches for our devices/boards:
https://lists.denx.de/pipermail/u-boot/2017-March/282789.html (AXP crashes) ;
Gbit ethernet patch for some LIME2 revisions ;
with SPI flash support
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
20 lines
770 B
20 lines
770 B
11 years ago
|
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.
|