From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/8] Introduce EDK2 firmware builds
Date: Mon, 20 Jul 2020 23:10:48 +0200 [thread overview]
Message-ID: <20200720231048.35f0aa60@windsurf.home> (raw)
In-Reply-To: <20200719180727.28202-1-hi@senzilla.io>
Hello Dick,
On Sun, 19 Jul 2020 18:08:13 +0000
Dick Olsson <hi@senzilla.io> wrote:
> One of the main reasons one would use EDK2 and UEFI on a AArch64 is for
> different standards compliance scenarios. The most prevalent standards in this
> space are:
>
> * Server Base System Architecture (SBSA) for hardware platforms
> * Server Base Boot Requirement (SBBR) for bootloader firmware
>
> This series introduces a new generic SBSA board called aarch64-sbsa which can
> be used by any configuration providing SBBR firmware.
>
> Three of the four configurations in this series implement SBBR firmware:
>
> 1. aarch_efi_defconfig: EDK2 as stand-alone flash device for QEMU Virt
> 2. qemu_aarch64_virt_sbbr_defconfig: EDK2 as ATF BL33 for QEMU Virt
> 3. qemu_aarch64_sbsa_sbbr_defconfig: EDK2 as ATF BL33 for QEMU SBSA
> 4. arm_foundationv8_sbbr_defconfig: EDK2 as ATF BL33 for ARM FVP
I must say my knowledge of SBBR/SBBA is very limited, but I'm confused
by the addition of all those configurations.
First of all, Buildroot doesn't really have a concept of a "board"
separated from a defconfig. It seems like you believe you have created
the support for a board by creating board/aarch64-sbsa/, but really the
support for a board in Buildroot is mainly a defconfig. So here, you
have adjusted one board configuration and created 3 new ones.
What is the Qemu SBSA platform compared to the QEMU Virt one ? Why
would we want qemu_aarch64_virt_sbbr_defconfig and
qemu_aarch64_sbsa_sbbr_defconfig ?
What makes these platform Qemu specific ? The fact that we do build
EDK2, which is the firmware, and therefore is obviously
board/platform-specific ? If that's the case how is EDK2 useful on the
aarch64_efi case, which is a cross-platform defconfig that should work
on any EFI-capable AArch64 system ?
I know, lots of questions there. Just trying to figure out how things
work, and what is the most relevant for Buildroot to handle this.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-07-20 21:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 18:08 [Buildroot] [PATCH 0/8] Introduce EDK2 firmware builds Dick Olsson
2020-07-19 18:08 ` [Buildroot] [PATCH 1/8] package/edk2-platforms: new package Dick Olsson
2020-07-20 20:40 ` Thomas Petazzoni
2020-07-19 18:09 ` [Buildroot] [PATCH 2/8] boot/edk2: " Dick Olsson
2020-07-20 20:56 ` Thomas Petazzoni
2020-07-19 18:09 ` [Buildroot] [PATCH 3/8] boot/arm-trusted-firmware: bump to version 2.2 Dick Olsson
2020-07-20 20:39 ` Thomas Petazzoni
2020-07-19 18:10 ` [Buildroot] [PATCH 4/8] boot/arm-trusted-firmware: add EDK2 as BL33 option Dick Olsson
2020-07-20 20:59 ` Thomas Petazzoni
2020-07-20 21:21 ` Yann E. MORIN
2020-07-21 7:26 ` Thomas Petazzoni
2020-07-19 18:10 ` [Buildroot] [PATCH 5/8] configs/aarch64_efi_defconfig: build the EDK2 firmware from source Dick Olsson
2020-07-20 21:02 ` Thomas Petazzoni
2020-07-19 18:10 ` [Buildroot] [PATCH 6/8] configs/qemu_aarch64_sbsa_sbbr_defconfig: new config for SBBR on QEMU SBSA Dick Olsson
2020-07-20 21:15 ` Thomas Petazzoni
2020-07-19 18:11 ` [Buildroot] [PATCH 7/8] configs/qemu_aarch64_virt_sbbr_defconfig: new config for SBBR on Virt Dick Olsson
2020-07-19 18:11 ` [Buildroot] [PATCH 8/8] configs/arm_foundationv8_sbbr_defconfig: new config for SBBR on FVP Dick Olsson
2020-07-20 21:10 ` Thomas Petazzoni [this message]
2020-07-22 19:36 ` [Buildroot] [PATCH 0/8] Introduce EDK2 firmware builds DO
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=20200720231048.35f0aa60@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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