public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, ray.ni@intel.com
Cc: "Zimmer, Vincent" <vincent.zimmer@intel.com>,
	"Ma, Maurice" <maurice.ma@intel.com>,
	"Rangarajan, Ravi P" <ravi.p.rangarajan@intel.com>,
	"Dong, Guo" <guo.dong@intel.com>,
	"Hau, Tze-ming" <tze-ming.hau@intel.com>
Subject: Re: [edk2-devel] RFC: Universal Payload Interface
Date: Tue, 27 Oct 2020 15:21:25 +0100	[thread overview]
Message-ID: <facb2b8a-6def-ee4d-0d60-b29216ec5add@redhat.com> (raw)
In-Reply-To: <CO1PR11MB4930E299B35B2E0CB4D7866F8C1A0@CO1PR11MB4930.namprd11.prod.outlook.com>

On 10/23/20 03:18, Ni, Ray wrote:
> With the fact that there are many different firmware implementations, we tried to decouple today's monolithic UEFI firmware binary to two independent components: bootloader and payload.

(1) "Bootloader" is an extremely loaded word. Regardless of everything
else in this topic, I strongly suggest picking a different name.

We already have "Platform Init" or "PI"; maybe use "Silicon Init" or "SI"?


(2) What is the *exact* use case (or workflow) that the proposed
interface enables, or improves?

What groups of people (what roles) are supposed to benefit from the
proposed interface?

Thanks
Laszlo

> 
> Basically, bootloader initializes the silicon hardware and payload prepares the OS required data and services. Bootloader passes control to payload.
> 
> https://universalpayload.github.io/documentation/spec/spec.html defines the universal interface between bootloader and payload. So that different bootloaders can work with different payloads, initializing different hardware and booting different OSes.
> The interface document is in very draft phase. Any feedback is welcome.
> 
> We also developed the POC code to demonstrate the idea. Please use below steps to get the code that uses SBL as the bootloader and EDKII UEFI Payload as the payload. This POC is being developed for QEMU Q35 virtual machine.
> 
>   1.  Run "git clone https://github.com/universalpayload/tools.git payload"
> 
> This step downloads the initial tools that will setup the dev environment.
> 
>   1.  Run "py -3 clone_and_build_sbl_with_uefipayload.py" in the "payload" directory
> 
> This script downloads branched SBL (https://github.com/universalpayload/slimbootloader.git) and edk2 (https://github.com/universalpayload/edk2.git).
> 
> Then it builds the firmware binary "SlimBootloader.bin" in "codeworkspace" directory.
> 
>   1.  Boot QEMU by running "qemu-system-x86_64.exe -machine q35 -pflash  codeworkspace\SlimBootloader.bin  -serial file:test.log"
> 
> Because the code is under active development, please contact us when you cannot build or boot successfully.
> 
> Besides the SBL, we modified coreboot (https://github.com/universalpayload/coreboot.git) to let it conform to the universal interface as a bootloader.
> Besides the EDK2 UEFI Payload, we created a payload (https://github.com/universalpayload/linuxpayload.git) that can boot Linux.
> 
> Thanks,
> Ray
> 
> 
> 
> 
> 
> 
> 


  reply	other threads:[~2020-10-27 14:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23  1:18 RFC: Universal Payload Interface Ni, Ray
2020-10-27 14:21 ` Laszlo Ersek [this message]
2020-10-28  3:26   ` [edk2-devel] " Ni, Ray
2020-11-02 14:49     ` Laszlo Ersek
2020-10-28 20:41 ` Carsey, Jaben
2020-10-28 20:51   ` Guo Dong

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-list 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=facb2b8a-6def-ee4d-0d60-b29216ec5add@redhat.com \
    --to=devel@edk2.groups.io \
    /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