From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 0/6] x86: efi: Add a 64-bit coreboot payload
Date: Mon, 6 Apr 2020 07:19:28 +0200 [thread overview]
Message-ID: <323cd31c-e7eb-bffc-7849-030ea11efe09@gmx.de> (raw)
In-Reply-To: <20200405232240.209612-1-sjg@chromium.org>
On 4/6/20 1:22 AM, Simon Glass wrote:
> This series creates a new 64-bit 'coreboot64' build which can be launched
> from coreboot. It uses SPL to effect the jump to 64-bit mode.
>
> This was done in an attempt to get the Ubuntu FirmwareTestSuite[1]
> working. Unfortunately the latest version shows a splash screen and hangs,
> perhaps due to some missing EFI support.
fwts exists as a snap package that can be run from the operating system.
I had not problem with running it on ARM64 systems. Cf.
https://snapcraft.io/fwts.
Do you relate to to the live image that gave you problems?
Best regards
Heinrich
>
> [1] https://wiki.ubuntu.com/FirmwareTestSuite
>
>
> Simon Glass (6):
> x86: Allow building an SPL image for coreboot
> x86: Move work-around out of cpu_jump_to_64bit_uboot()
> x86: Update SPL for coreboot
> x86: cbfs: Drop unwanted declaration
> x86: coreboot: Allow building an SPL image
> x86: Add a 64-bit coreboot build
>
> Makefile | 6 ++++
> arch/x86/cpu/Makefile | 4 ++-
> arch/x86/cpu/coreboot/Kconfig | 1 +
> arch/x86/cpu/coreboot/Makefile | 8 ++++-
> arch/x86/cpu/coreboot/coreboot.c | 3 +-
> arch/x86/cpu/coreboot/coreboot_spl.c | 12 +++++++
> arch/x86/cpu/i386/cpu.c | 10 ------
> arch/x86/cpu/intel_common/Makefile | 2 ++
> arch/x86/cpu/x86_64/cpu.c | 2 ++
> arch/x86/dts/coreboot-u-boot.dtsi | 18 +++++++++++
> arch/x86/lib/spl.c | 23 ++++++++++---
> board/coreboot/coreboot/MAINTAINERS | 7 ++++
> configs/coreboot64_defconfig | 48 ++++++++++++++++++++++++++++
> doc/board/coreboot/coreboot.rst | 10 ++++++
> include/cbfs.h | 2 +-
> 15 files changed, 138 insertions(+), 18 deletions(-)
> create mode 100644 arch/x86/cpu/coreboot/coreboot_spl.c
> create mode 100644 arch/x86/dts/coreboot-u-boot.dtsi
> create mode 100644 configs/coreboot64_defconfig
>
next prev parent reply other threads:[~2020-04-06 5:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 23:22 [PATCH 0/6] x86: efi: Add a 64-bit coreboot payload Simon Glass
2020-04-05 23:22 ` [PATCH 1/6] x86: Allow building an SPL image for coreboot Simon Glass
2020-04-23 9:14 ` Bin Meng
2020-04-26 19:45 ` Simon Glass
2020-04-05 23:22 ` [PATCH 2/6] x86: Move work-around out of cpu_jump_to_64bit_uboot() Simon Glass
2020-04-23 9:16 ` Bin Meng
2020-04-26 19:45 ` Simon Glass
2020-04-27 1:47 ` Bin Meng
2020-04-27 3:00 ` Simon Glass
2020-04-05 23:22 ` [PATCH 3/6] x86: Update SPL for coreboot Simon Glass
2020-04-05 23:22 ` [PATCH 4/6] x86: cbfs: Drop unwanted declaration Simon Glass
2020-04-23 9:19 ` Bin Meng
2020-04-23 9:32 ` Bin Meng
2020-04-05 23:22 ` [PATCH 5/6] x86: coreboot: Allow building an SPL image Simon Glass
2020-04-05 23:22 ` [PATCH 6/6] x86: Add a 64-bit coreboot build Simon Glass
2020-04-23 9:29 ` Bin Meng
2020-04-26 19:45 ` Simon Glass
2020-04-06 5:19 ` Heinrich Schuchardt [this message]
2020-04-06 14:28 ` [PATCH 0/6] x86: efi: Add a 64-bit coreboot payload Simon Glass
2020-04-17 15:31 ` Andy Shevchenko
2020-04-23 8:05 ` Bin Meng
2020-04-24 6:01 ` Heinrich Schuchardt
2020-04-24 9:28 ` Andy Shevchenko
2020-04-24 14:08 ` Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=323cd31c-e7eb-bffc-7849-030ea11efe09@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox