From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/6] x86: efi: Add a 64-bit coreboot payload
Date: Fri, 24 Apr 2020 12:28:07 +0300 [thread overview]
Message-ID: <20200424092807.GZ185537@smile.fi.intel.com> (raw)
In-Reply-To: <0b67f8f2-fe6e-65b8-994b-f712dac929bb@gmx.de>
On Fri, Apr 24, 2020 at 08:01:32AM +0200, Heinrich Schuchardt wrote:
> On 4/23/20 10:05 AM, Bin Meng wrote:
> > Hi Simon,
> >
> > On Mon, Apr 6, 2020 at 7:22 AM Simon Glass <sjg@chromium.org> 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.
> >
> > Adding 64-bit U-Boot as a coreboot payload is nice.
> >
> >>
> >> This was done in an attempt to get the Ubuntu FirmwareTestSuite[1]
> >
> > Yet I fail to understand why adding 64-bit U-Boot as the coreboot
> > payload could help running the Ubuntu Firmware Test Suite. Does 32-bit
> > U-Boot as the coreboot payload not work in this case?
>
> coreboot_defconfig has CONFIG_EFI_LOADER=y so the firmware test suite
> should work fine if you are running a 32 bit OS.
>
> Of cause calling a 32bit UEFI from a 64bit OS is expected fail due to a
> different ABI.
I'm wonder how Linux (64-bit) kernel with EFI stub enables boots on EFI 32-bit environment?
> >> working. Unfortunately the latest version shows a splash screen and hangs,
> >> perhaps due to some missing EFI support.
> >>
> >> [1] https://wiki.ubuntu.com/FirmwareTestSuite
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-04-24 9:28 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 ` [PATCH 0/6] x86: efi: Add a 64-bit coreboot payload Heinrich Schuchardt
2020-04-06 14:28 ` 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 [this message]
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=20200424092807.GZ185537@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--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