# 2022-04-06 - coreboot Leadership Meeting Minutes
Next meeting - 2022-04-20 - See the calendar on the coreboot website for more information.
## Attendees Felix Held, Jay Talbott, Arthur Heymans, David Hendricks, Christian Walter, Stefan Reinauer, Lean Sheng Tan, Martin Roth, Matt Papageorge, Piotr Krol, Tim Crawford, Julius Werner, Felix Singer, Patrick Georgi
## Decisions * Let’s look at adding code to be able to combine romstage and ramstage. This is similar to what is currently done with combining verstage with either romstage or bootblock. * Send out surveys to coreboot consultants. * No reason to move Quark to a branch unless there's actually an issue. Felix S will link to the problematic code.
## Minutes * [Arthur] Let's look at a single stage (ramstage) on AMD platforms * We discussed a hybrid romstage before, but we really only need a ramstage at this point. None of the currently required code really needs to be in romstage however. We can move all of the required code into ramstage, which would dramatically simplify the code by removing everything passing between stages. * One stage means we can reference symbols directly without requiring linker scripts, cbmem additions, etc. * How would this work with Ron’s idea of getting rid of ramstage? * It would generally be a different configuration. * How much re-architecture would this require? * The idea wasn’t to rearchitect coreboot, just to add the calls that would normally happen in romstage to the beginning of ramstage. * Make ramstage callable as a function rather than treating it as a separate blob to jump to. * Let’s not make this a requirement or try to move all platforms to this flow.
* [Martinr] Coreboot approved vendors - update website. * Send out a survey to all coreboot consultants.
* [Julius]: libpayload CBFS API deprecation; please port payloads to new API. See the notice on the mailing list for more information. [1]
* [Martin]: Moving Quark to a branch. [2] * We’re not “Deprecating platforms”, we’re moving their support to a branch. * [Jay]: Syspro has pushed a number of platform changes to the 4.11 branch. Supporting platforms there is not a problem. * Why would we move this out of the main branch? It uses FSP 2.0, and it’s the only open source fsp. * [Felix S] There’s some quark-only code that should probably be improved if quark is not getting removed.
* [Martin] See if we can gather some information about what’s getting built to help decide what’s not actually being used anymore. * Would need to consult lawyers * This might cause more confusion than we even have
* [Arthur] Update sdk docker for latest clang * This will be updated this week.
* [FelixS] Thinking about doing a firmware hackathon in Darmstadt, Germany. Poll and some more details at the link. [3] * [Chris] 9elements / Foundation can sponsor food/place/whatever * @Felix - Get in contact with Sheng or Chris on that * This would happen June 10 - 12 June
* [Jay]: Martin, any sign of the ITRenew server? * Not yet. :(
* [David]: Porting Up Extreme to coreboot - whiskey lake platform * Having issues flashing with a dediprog * The UP Extreme boards have a unique port for flashing that needs an adapter. * 9elements has adapters that will make this work. * Can we figure out a way that people can get these created easily? * qspimux: https://github.com/felixheld/qspimux * David had issues getting the qspiMux boards manufactured at oshpark. Outlines too close to board edge - small violations of design rules, probably due to the castellated holes on the board adapters; that usually costs extra and not all manufacturers can do that.
# Next meeting * The coreboot leadership meeting minutes are available here: [4] * The next coreboot leadership meeting will be 2022-04-20: [5]
# 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.
[1]: https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/VLMKV... [2]: https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/YRJQI... [3]: https://terminplaner4.dfn.de/pBooK8FBDlM2zDwa [4]: https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKj... [5]: https://calendar.google.com/event?action=TEMPLATE&tmeid=MzNhYm9rMmtxMnU1...