EBBR Notes 2021 11 08

Weekly meeting notes

Attendees

From SUSE
- Noticed that we were using Tumbleweed. Are we planning to use any other releases?
  - Any well recognized Linux distro edition can be used. Some boards have been certified using Leap for example
From Simon
- (with open source hat on) Wouldn't an open source build be preferrable?
- How do we know what source the image is built from?
- Grant: The program is designed around ODMs providing firmware binaries because we want to be testing the firmware that is actually being shipped on the board.
  - Don't currently have any way to validate the source tree that goes with that firmware
  - It is a gap in the current program
From Etienne
- There are fewer generic distros available for 32 bit, how will this affect certification?
- Grant: I'm hoping to have a generic Yocto build that can be used on 32-bit
- Debian supports 32-bit, but need to check if they have a suitable image
- Matthias: OpenSUSE will still be supporting 32-bit

Features for IR 2.0

Went through Arm's list
Darren: How do we support accelerators?
- ATM, IR certification doesn't require any device support except what is required for boot
Action: Grant to add list of EBBR spec changes that Arm is interested in (see below)
Homework for all: Think about what you'd like to see in IR 2.0 and report back at next meeting

Arm's list of potential EBBR updates (draft & under investigation):

Require network boot (TCP, TLS, HTTPS)
Start requiring some BSA items
Require DT schema conformance testing
Require UEFI Secure Boot
Require signed and verified firmware updates
Require FIDO Device Onboarding
Improved Boot Device Selection (replacing hush script implementation)
Require variable storage outside System Partition
Require SetVariable() after ExitBootServices() -- technically difficult, unlikely in the short term
Require ESRT and FWUPD integration testing
Define requirements when a display is enabled
Add power management requirements