Hi,

following the proposal at the last Device Tree Evolution call I'd like to propose an agenda for Wednesday that Steve could complement (see below). You may want to add or remove agenda items...

We need to synchronize with "kernel day" agenda as some of us need to attend both events.

Cheers

FF

4h: DeviceTree Lead Project

-

to be defined by Steve McIntyre

4h: DependableBoot Lead Project

-

1h: status and deliverable planning for next cycle -

EBBR specs next steps? compliance. -

UEFI SecureBoot -

EFI payload authentication -

UEFI Secure variable handling -

Linux kernel UEFI variable caching and updates (as a capsule update) -

Define other ‘must-have’ UEFI features (i.e DBT??) -

firmwareTPM -

UEFI MeasuredBoot -

32bits UEFI support -

Qemu EBBR -

implications of our work on EDKII -

1h: Robust boot "research" & PoC for next cycle -

anti-brickable incl. TF-A: “philosophy” and hints to implement -

UEFI watchdog: when to call UEFI exit-boot-services? -

2h: overall boot architecture evolution -

interdependencies between TF-A, TrustZone (SPM, OPTEE, SCPI), OS, SCMI - many things are happening and I am not sure we understand tricky interactions that may result in race conditions (for instance SCMI in OPTEE kernel and its relations with UEFI runtime services). The idea is to try to identify the hairiest issues that we should analyze post Connect. -

Boot orchestration -

"Contracts" / list all the assumptions