EBBR Notes 2024.04.08

Attendees

No general agreement that the footnotes proposed in #117 actually help; dropped.
Agreement to merge #123 after the version 2.2 change mentioned in the comments has been done.
Agreement to merge #121.
Agreement that an EBBR release 2.2 can be prepared for review after the aforementioned actions have been adressed.
Discussions around a U-Boot regression in the UEFI boot manager.

Pull #117: Request-for-comments about moving away references to footnotes
- -> drop it
Pull #123: Provision conformance profile guid
- Action: Vincent to s/TBD/2.2/, then merge.
Pull #121: Require the TCG2 protocol if system has a TPM (issue #65)
- "if TPM then -> must implement TCG2"
- Agreed; action Vincent -> merge
EBBR release
- #119 needs to be refined -> it is out of next release
- #118 is nice to have; does not block next release
- #108 discussion in SysArchAc not settled; wait a bit -> is out of next release
- #106 is nice to have; does not block next release
- -> address actions then release
Last U-Boot release; boot manager regression
- Are we testing Boot#### / BootNext / etc. in SCT/ACS?
- Solution close; needs to "ripple down" into efi var lib and the distros
- In SCT: uefi-sct/SctPkg/TestCase/UEFI/EFI/Generic/EfiCompliant/BlackBoxTest/EfiCompliantBBTestRequired_uefi.c
- We might be missing some coverage in SCT...
- We need a test inside U-Boot
  - UEFI selftest is maybe not suitable due to the reset, though.
  - A python test might be better. Use one UEFI binary, with a boot option passing a string, printed by the binary. "bootefi helloworld" could do? There is also a separate helloworld UEFI binary -> create a disk image with it. Could rename to hello1, hello2 and hello3 and we could test the devicepath, too.