2025-02-19 - coreboot Leadership Meeting Minutes

# 2025-02-19 - coreboot Leadership Meeting

## Attendees

Felix Singer, Andre, Martin Roth, David Hendricks, Alicja Michalska, Julius Werner, Werner Zeh,
Matt DeVillier, Andy Ebrahiem, Mina Asante, Karthik Ramasubramanian, Jeremy Compostella.

## Open Action Items

* 2024-11-27
    * [Open] Send out poll with regards to  LLM usage (requested by SFC)
  * 2024-10-30
    * [Open] Add clarification to docs, “do not use gerrit change-id or CB: format in reference to
already-merged patches”.
  * 2024-10-16
    * [Open] Matt: Set up a meeting to discuss board status alternatives and send out invites. 
      * Decouple data collection with uploading
      * Require gerrit credentials or other auth to push
      * Json format?
      * https://github.com/chrultrabook/linux-tools/blob/main/debugging.sh
  * 2024-09-18
    * [Open] Jon: Schedule a dedicated meeting to discuss the Coverity defects and action plan.
      * Werner: Send out an invite for the meeting. 
        Sent out a poll to find a time slot: https://rallly.co/invite/1c8J3azXAcje
  * 2024-05-01
    * [Open] Nick Van Der Harst volunteered for Dutch. "gogo gogo" would like to translate to Russian
(?)
  * 2024-01-10
      * Nico: (https://review.coreboot.org/q/topic:enforce_region_api)
          *  [Open] Daniel: Look at how we want to localize (non-console) strings for coreboot. Long term
project.

## Minutes

### [Werner] Update on Intel’s plans around signing their FSP binaries
  * Currently not POR for API-mode binary, only for dispatch mode
  * It should not impact the coreboot flow. However, NDA customers need to keep an eye on it since if
it does impact coreboot then that will be a drastic change.
    * Doc #830299 and #827444

### [David] Change in coreboot leadership
  * Martin Roth will take my spot

### [Martin] AMD releasing Phoenix and Turin OpenSIL
  * Hopefully in February or early March
    * Somewhat more detail: (https://github.com/openSIL/openSIL/issues/24)
  * It'll be a while before releasing another one as they switch from proof-of-concept (POC) to
plan-of-record (POR), migrating from AGESA to OpenSIL on next-gen SOCs.
  * Limits of POC
    * No graphics init, but could use the GOP driver with some effort in creating a wrapper.
  * Graphics init will be done in GOP driver (UEFI-specific) moving forward
    * coreboot needs a way to deal with this
    * We have yabel, x86emu, etc. for legacy graphics init.
  * uGOP or previous efforts?
    * AMD doesn't do graphics init before memory is up.
    * uGOP replaced open-source graphics init, which is the cause of the earlier pushback.
  * [Alicja] u-boot might have a workable solution?
    * Need to see what the current status is and potentially borrow parts of it to deal with graphics init.
  * Linux might be able to init graphics, but AtomBIOS tables still need to be filled in for kernel drivers to read.
    * [Alicja] On Intel side, there are video BIOS tables as well that fills in things like ports
present. Alicja has gotten this working with coreboot + EDK2 by using GOP driver.
    * [Martin] Another option is to run GOP driver once in the tianocore payload to generate AtomBIOS
tables, store the info, and then skip GOP driver on subsequent boots.
      * It's just a 64KiB chunk of data.
  * People with AMD NDA support can get a customized AtomBIOS table for their platform. Workarounds
to run the GOP driver are more for the community to use.

# Next Leadership Meeting
  * March 5, 2025.
  * [coreboot Calendar](https://coreboot.org/calendar.html).

# Notice
Decisions shown here are not necessarily final, and are based on the current information available.
If there are questions or comments about decisions made, or additional information to present, 
please put it on the leadership meeting agenda and show up if possible to discuss it. 
Of course, items may also be discussed on the mailing list, but as it's difficult to interpret 
tone over email, controversial topics frequently do not have good progress in those discussions. 
For particularly difficult issues, it may be best to try to schedule another meeting.

# coreboot leadership meeting minutes
https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKj...