Eric Lee / smarc-uboot

Download as
Browse Code ยป

Commit 40144260a9c8c5228500824ad9b7b19597a4bb0b

Authored by Bin Meng
1 parent 73149164f4
Exists in smarc_8mq_lf_v2020.04 and in 11 other branches 8qm-imx_v2020.04_5.4.70_2.3.0, emb_lf_v2022.04, pitx_8mp_lf_v2020.04, smarc-8m-android-10.0.0_2.6.0, smarc-8m-android-11.0.0_2.0.0, smarc-8mp-android-11.0.0_2.0.0, smarc_8m-imx_v2019.04_4.19.35_1.1.0, smarc_8mm-imx_v2019.04_4.19.35_1.1.0, smarc_8mm-imx_v2020.04_5.4.24_2.1.0, smarc_8mp_lf_v2020.04, smarc_8mq-imx_v2020.04_5.4.24_2.1.0

doc: vxworks: Mention chain-loading an x86 kernel via 'bootefi' 

This updates the doc to mention chain-loading an x86 kernel via
'bootefi' command, along with several typos fix.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Alexander Graf <agraf@suse.de>

Showing 1 changed file with 12 additions and 6 deletions Side-by-side Diff

1 1 # SPDX-License-Identifier: GPL-2.0+
2 2 #
3 3 # Copyright (C) 2013, Miao Yan <miao.yan@windriver.com>
4   -# Copyright (C) 2015, Bin Meng <bmeng.cn@gmail.com>
  4 +# Copyright (C) 2015-2018, Bin Meng <bmeng.cn@gmail.com>
5 5  
6 6 VxWorks Support
7 7 ===============
8 8  
... ... @@ -15,10 +15,13 @@
15 15 on other architectures, 'bootvx' shall be used. For booting VxWorks 7 kernels
16 16 on PowerPC and ARM, 'bootm' shall be used.
17 17  
  18 +With CONFIG_EFI_LOADER option, it's possible to chain load a VxWorks x86 kernel
  19 +via the UEFI boot loader application for VxWorks loaded by 'bootefi' command.
  20 +
18 21 VxWorks 7 on PowerPC and ARM
19 22 ---------------------------
20   -From VxWorks 7, VxWorks starts adopting device tree as its hardware decription
21   -mechansim (for PowerPC and ARM), thus requiring boot interface changes.
  23 +From VxWorks 7, VxWorks starts adopting device tree as its hardware description
  24 +mechanism (for PowerPC and ARM), thus requiring boot interface changes.
22 25 This section will describe the new interface.
23 26  
24 27 For PowerPC, the calling convention of the new VxWorks entry point conforms to
... ... @@ -53,6 +56,9 @@
53 56 When using 'bootm', just define "bootargs" in the environment and U-Boot will
54 57 handle bootline fix up for the kernel dtb automatically.
55 58  
  59 +When using 'bootefi' to chain load an x86 kernel, the UEFI boot loader
  60 +application for VxWorks takes care of the kernel bootline preparation.
  61 +
56 62 Serial console
57 63 --------------
58 64 It's very common that VxWorks BSPs configure a different baud rate for the
... ... @@ -63,9 +69,9 @@
63 69  
64 70 x86-specific information
65 71 ------------------------
66   -Before loading an x86 kernel, one additional environment variable need to be
67   -provided. This is "vx_phys_mem_base", which represent the physical memory
68   -base address of VxWorks.
  72 +Before direct loading an x86 kernel via 'bootvx', one additional environment
  73 +variable need to be provided. This is "vx_phys_mem_base", which represent the
  74 +physical memory base address of VxWorks.
69 75  
70 76 Check VxWorks kernel configuration to look for LOCAL_MEM_LOCAL_ADRS. For
71 77 VxWorks 7, this is normally a virtual address and you need find out its