-
Notifications
You must be signed in to change notification settings - Fork 36
EBBR Notes 2020.12.14
Grant Likely edited this page Dec 14, 2020
·
3 revisions
- Ilias Apalodimas (Linaro)
- Grant Likely (Arm)
- Joakim Bech (Linaro)
- Mark Brown (Arm)
- Simon Glass (Google)
- Daniel Thompson (Linaro)
- Vincent Stehlé (Arm)
- Jose Marinho (Arm)
- Bill Mills (Linaro)
- Atish
- Heinrich
- EBBR Compliance Testing Activity (Heinrich)
- Round table
- Any other business
Next meeting: 18 Jan
U-Boot Status Update, Heinrich Schuchardt
- Heinrich's presentation on U-Boot updates in general and Device tree fixup EBBR is a nice placeholder before this goes into the EFI spec Atish: Is there a reason to go via EBBR and not sending it to EFI directly? Heinrich: There no notion of DTB in EFI at the moment, we could do once DTs are included in the spec
U-Boot main updates on EFI Sughosh and Takahiro working on CapsuleUpdates and FMP Ilias working on EFI_TCG2 protocol and SetVariable as a runtime service for U-Boot Heinrich working on SCT and Loadfile2 Protocol Current status on SCT results: https://github.com/U-Boot-EFI/u-boot-sct-results
Discussion on implementation of SetVariable() options discussion
- Ilias gave overview of SetVariable() work and the options for implementing at runtime
- Discussion about whether or not EBBR should require SetVariable
- Pros: Distros just work, consistency with desktop/server/SBBR
- Cons: Technically difficult, Unresolved implementation problems, incompliant with spec, disqualifies many platforms for SystemReady-IR certification
- For time being SetVariable after EBS() should remain optional
- Outstanding issue to be resolved before next EBBR release: Must have recommended alternative method for modifying boot flow when SetVariable after EBS() not available.