Skip to content

EBBR Notes 2024.03.11

Jump to bottom Edit New page
Vincent Stehlé edited this page Mar 12, 2024 · 5 revisions

Attendees

  • Heinrich Schuchardt (Canonical)
  • Ilias Apalodimas (Linaro)
  • Etienne Carrière (STMicroelectronics)
  • Jon Humphreys (TI)
  • Vincent Stehlé (Arm)

Agenda

  • Next EBBR release schedule
  • Upstreaming /chosen/efivarfile definition to dt-schema
  • Pull #120: Clarify that ConnectController must be implemented (call of 15 Jan, issue #114)
  • Pull #108: Require smbios
  • Pull #119: Require authenticated capsules
  • Pull #121: Require the TCG2 protocol if system has a TPM (issue #65)
  • Pull #117: Request-for-comments about moving away references to footnotes
  • Pull #118: Request-for-comments about adding version annotations

Notes

  • Agreement that an EBBR release makes sense; sort out what is in and what is out
  • Remove wording about /chosen/efivarfile for now
  • Agreement to merge pull #120
  • Respin pull #108 and discuss further
  • Revisit pull #119 with A/B update in mind
  • Interest for pull #118; continue in that direction
  • Reminder: EBBR call will be on BST starting 31 March

Raw notes

  • Next EBBR release schedule
    • Changes captured in commit 2a60aad30c84
    • A release makes sense, at least for the EFI variables file format
    • The sooner the better, but see each in-flight item and see if it is a must have
  • Upstreaming /chosen/efivarfile definition to dt-schema
    • If you have edk2, preferable to define a config table? edk2 mostly ACPI
    • U-Boot + Qemu even pass-through ACPI tables
    • Discuss on the next call with Ilias' presentation to support
    • Solution before release? Not
    • Action Vincent -> Remove /chosen/efivarfile before release
  • Pull #120: Clarify that ConnectController must be implemented (call of 15 Jan, issue #114)
    • Pull request is enough -> merge
  • Pull #108: Require smbios
    • We could strongly recommend instead -> Action: Vincent respin
      • if implemented, then ... those structures are required ("at least")
    • Useful to identify systems (useful for metal as a service, fleet of devices), arch agnostic in EBBR
    • Is Type 32 containing meaningful information in U-Boot today?
      • Do not require it?
    • Simply refer to SMBIOS Table 4 – Required structures and data
      • Which ones are actually used by the OS?
      • Add the missing ones to U-Boot (Types 19 & 32)
    • Delay decision; ping Peter
  • Pull #119: Require authenticated capsules
    • Problem with A/B update; the empty capsules do not have FMP or authentication
      • Could allow to fake A/B response
      • Acceptance capsule should be downloaded from a server? Or should it work offline?
      • With the version, can ensure a single acceptance capsule for a single update (no replay)
      • Need to verify if unsigned acceptance capsule is ok
      • Change
        • The firmware shall accept only authenticated updates.
        • ...to the firmware (or similar)?
      • Revisit with A/B update in mind, with Jose.
  • Pull #118: Request-for-comments about adding version annotations
    • Interesting to have the information
    • How do we phrase those informations? Continue to work on it
  • EBBR call and BST
    • BST will start on 31 March

Links

Add a custom footer
Add a custom sidebar
Clone this wiki locally