On Fri, Apr 13, 2018 at 12:42 AM, Simon Glass <s...@chromium.org> wrote: > On 11 April 2018 at 23:02, Bin Meng <bmeng...@gmail.com> wrote: >> When booting from EFI BIOS, VxWorks bootloader stores the EFI GOP >> framebuffer info at a pre-defined offset @ 0x6100. When VxWorks >> kernel boots up, its EFI console driver tries to find such a block >> and if the signature matches, the framebuffer information will be >> used to initialize the driver. >> >> However it is not necessary to prepare an EFI environment for >> VxWorks's EFI console driver to function (eg: EFI loader in >> U-Boot). If U-Boot has already initialized the graphics card and >> set it to a VESA mode that is compatible with EFI GOP, we can >> simply prepare such a block for VxWorks. >> >> Signed-off-by: Bin Meng <bmeng...@gmail.com> >> --- >> >> Changes in v2: None >> >> cmd/elf.c | 19 +++++++++++++++++++ >> include/vxworks.h | 26 ++++++++++++++++++++++++++ >> 2 files changed, 45 insertions(+) > > Reviewed-by: Simon Glass <s...@chromium.org>
applied to u-boot-x86, thanks! _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
