Skip to content

Introduce EDK2 firmware builds

Thomas Petazzoni buildroot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest7 of 8 patches 0 repliesNew

7 of 8 patches are in this archive. The cover letter announces 8.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/8package/edk2-platforms: new package+0 -00 replies
2/8boot/edk2: new package+0 -00 replies
3/8boot/arm-trusted-firmware: bump to version 2.2+0 -00 replies
4/8boot/arm-trusted-firmware: add EDK2 as BL33 option+0 -01 reply
4/8boot/arm-trusted-firmware: add EDK2 as BL33 option+0 -00 replies
5/8configs/aarch64_efi_defconfig: build the EDK2 firmware from source+0 -00 replies
6/8configs/qemu_aarch64_sbsa_sbbr_defconfig: new config for SBBR on QEMU SBSA+0 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Buildroot] [PATCH 0/8] Introduce EDK2 firmware builds

Hello Dick,

Quoted 10 lines · On Sun, 19 Jul 2020 18:08:13 +0000 Dick Olsson <[email protected]> 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.

Quoted 6 lines

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

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com