August 2024 - coreboot - mail.coreboot.org

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org Aug. 9, 2024

Aug. 9, 2024

Hello coreboot community, We are doing a group review session next wednesday: https://meet.google.com/kpu-yozw-gtt. Check the coreboot calendar for the time in your timezone: https://coreboot.org/calendar.html We’ll be reviewing a few RFC patches together, then switch to reviewing patches individually for a bit, but everyone will be available if you have questions about the patch you’re reviewing. Here’s the link to the list of patches to be reviewed: https://docs.google.com/spreadsheets/d/1io-tewVlkX3PAkhR9ttCKjJXiXR9Emy6qsY… If you have patches that you’d specifically like to have reviewed by the group, please add them to the top of the sheet. We are obviously limited on time during the review session, so any reviews that are done before the session are appreciated. We definitely don’t expect to get everything reviewed. Thank you very much, we hope to have a good turnout. Best regards, Mina.

1 0

2024-08-07 - coreboot Leadership Meeting Minutes
by mina＠coreboot.org Aug. 8, 2024

Aug. 8, 2024

# 2024-08-07 - coreboot Leadership Meeting ## Attendees Martin Roth, Matt DeVillier, Felix Held, Jay Talbott, Max Brune, Karthik Ramasubramanian, Mina Asante, David Hendricks, Julius Werner, Ron Minnich. ## Announcements & Events * OSFC will be in Bochum Germany - September 3-5 https://www.osfc.io * OCP Global Summit: San Jose, California on October 15–17, 2024 https://www.opencompute.org/summit/global-summit ## Open Action Items * 2024-05-01 * Nick Van Der Harst volunteered for Dutch. "gogo gogo" would like to translate to Russian (?) * 2024-03-20 * Martin:To Add a note to the gerrit guidelines to email the leadership for further discussion and guidance when code submissions are not up to standard. * 2024-03-06 * Martin: To update gerrit contributing guidelines documentation. (https://doc.coreboot.org/contributing/index.html) * 2024-01-10 * Nico: [https://review.coreboot.org/q/topic:enforce_region_api] * Daniel: Look at how we want to localize (non console) strings for coreboot. Long term project. ## Minutes ### [Max] RISC-V Architecture * Our RISC-V architecture is not really in a good shape. I have added a few patches over the last few months, but it is hard to find reviewers here, because there is not a single vendor that actually uses RISC-V on coreboot. So I would like to get temporary permission to merge my own patches. We don’t have any vendor depending on the architecture and the mainboards haven’t worked for months if not longer so I assume there are also not many other depending on it. Just to clarify I only ask permission to merge my own patches as long as they don’t influence code outside of RISC-V. My goal is to get the architecture properly running for actual hardware and QEMU. We can also add a restriction that I am only allowed to merge them if they haven’t been reviewed for ~1 month. I am not in a hurry anyway, but I would like to see them merged at some point. * [Martin] Ron might be able to help review the RISC-V portion. I still think we should have reviewers evaluate the patches. I’d be happy to help review patches for things other than evaluating correctness of the RISC-V architecture. * [Martin] Should we find a platform to port as our eval board for RISC-V? * Currently we have 2 platforms, and soon will have 4. * FelixH: would rather get at least one reviewer. * Add to the bi-weekly review list if needed. ### [Martin] coreboot Patches Review. * Last week’s review hour worked pretty well - there were about 6 of us on the call. We reviewed RFC patches together for about 40 minutes and then separated to review individual patches. The general feeling was that it was useful and that we should continue. * If there are any patches that people specifically want reviewed, add them to the list when it’s sent out. * The goal of that meeting is to help get patches merged. * Let us know if you want to be invited. * Or go to [https://coreboot.org/calendar.html] and add yourself * Martin: I don’t think this works - I believe only guests can modify the event to add other guests. * We’ll generate a list of patches we plan to review the week before the meeting - hopefully those can be looked at in the week before the meeting. * WIP patches will not be reviewed, with the exception of RFC patches. * The general search for patches we'll be reviewing: * repo:coreboot AND status:open AND age:1week AND -age:6months AND -is:wip AND -has:unresolved AND -label:Code-Review-1 AND -label:Verified-1 AND -is:wip ### coreboot 24.08 Release * Next release is planned to be tagged on 2024_08_22, the day after the next leadership meeting. This is 1 week later than initially planned to allow more time for testing. * Please mark anything you want to be merged with the hashtag “coreboot_release_24.08” * Mark anything that should be merged after the release with the hashtag "post_coreboot_release_24.08". ### [DavidH]: Looking at linkedin - Intel just cut a huge chunk of the workforce. Dell too. Please post any jobs you know of. * 9elements Open Positions: [https://9esec.io/team] # Next Leadership Meeting * August 21,2024. * [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 [2024-08-07](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1….

1 0

Incorrect Intel GPU IDs for Comet Lake CPUs
by Maxim Polyakov Aug. 7, 2024

Aug. 7, 2024

It seems that some of the graphics device IDs for intel Comet Lake CPUs are incorrect. According to the supported GPU list [1], fixed them in https://review.coreboot.org/c/coreboot/+/83708. If you support a motherboard with -S or -H processors, then please take a look at this patch. And it would be great if someone from Intel checked out these changes. Thx [1] https://web.archive.org/web/20240731152818/https://dgpu-docs.intel.com/devi… // Regards, // Max

1 0

[coreboot - Feature #420] (New) Use standard format of TPM event log
by Krystian Hebel Aug. 7, 2024

Aug. 7, 2024

Issue #420 has been reported by Krystian Hebel. ---------------------------------------- Feature #420: Use standard format of TPM event log https://ticket.coreboot.org/issues/420 * Author: Krystian Hebel * Status: New * Priority: Normal * Target version: none * Start date: 2022-10-12 * Related links: [1] https://trustedcomputinggroup.org/wp-content/uploads/TCG_PCClientImplementa… [2] https://trustedcomputinggroup.org/wp-content/uploads/TCG_PCClient_PFP_r1p05… ---------------------------------------- Currently coreboot uses proprietary format for TPM event log. TCG has standardized log formats, differently for TPM1.2 (aka legacy or SHA1) [1] and TPM2.0 (aka crypto agile) [2], both of which can be parsed by Linux kernel and exposed in sysfs. I don't know of any tool outside of cbmem which can parse coreboot format; this includes payloads which may be interested in continuing chain of trust started by coreboot. Another incompatibility is caused by vboot's assignment of PCRs. Roles of PCRs are roughly specified by TCG in both of mentioned documents, they are more or less compatible with each other, but not with current coreboot code. These changes could break assumptions made by existing platforms, so they should be made as Kconfig options. This is a tracking issue to collect subtasks that need to be done in order to support standard event log formats. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

4 12

24.08 release schedule
by coreboot org Aug. 7, 2024

Aug. 7, 2024

Hello coreboot, This is the notification that we're two weeks away from doing the coreboot 24.08 release tag, which is scheduled for Thursday August 22nd. Please mark patches you want to be merged before the release with the hashtag “coreboot_release_24.08”. There's no promise that these will get merged, but we try to get everything on the list in. Mark any patches that should be merged *after* the release with the hashtag "post_coreboot_release_24.08" As usual, we will have a 1 week delay after the new version is tagged to allow for testing of the release. This will give us a chance to fix any issues that are found during the release process before making the release public. The 24.08 public announcement is scheduled for August 29th. If you have any questions or concerns, please let the coreboot release team know. Martin

1 0

FLOSS firmware status on new Qualcomm Snapdragon X Elite devices
by Paul Menzel Aug. 7, 2024

Aug. 7, 2024

Dear coreboot folks, What parts of the firmware of the new Qualcomm Snapdragon X Elite devices, like Dell XPS 13 9345 [1], are FLOSS? Are these ARM devices good coreboot targets? Kind regards, Paul PS: With this new architecture, was coreboot/U-Boot ever considered, or is the x86 ecosystem of independent BIOS vendors (IBVs) so dominant, that no alternatives were considered? [1]: https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=h0v…

1 0

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org Aug. 5, 2024

Aug. 5, 2024

Dear coreboot community, Please be reminded that our upcoming leadership meeting is scheduled for Wednesday, August 7, 2024.[1] Kindly take a moment to review the current agenda and share your thoughts or suggest issues you would like to see discussed during the meeting.[2] Thank you. ## Current Agenda Items * [Max] RISC-V Architecture * Our RISC-V architecture is not really in a good shape. I have added a few patches over the last few months, but it is hard to find reviewers here, because there is not a single vendor that actually uses RISC-V on coreboot. So I would like to get temporary permission to merge my own patches. We don’t have any vendor depending on the architecture and the mainboards haven’t worked for months if not longer so I assume there are also not many other depending on it. Just to clarify I only ask permission to merge my own patches as long as they don’t influence code outside of RISC-V. My goal is to get the architecture properly running for actual hardware and QEMU. We can also add a restriction that I am only allowed to merge them if they haven’t been reviewed for ~1 month. I am not in a hurry anyway, but I would like to see them merged at some point. ## Announcements & Events * OSFC will be in Bochum Germany - September 3-5, 2024 https://www.osfc.io * OCP Global Summit: San Jose, California on October 15–17, 2024 https://www.opencompute.org/summit/global-summit [1](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkK…. [2](https://coreboot.org/calendar.html).

1 0

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org Aug. 2, 2024

Aug. 2, 2024

Dear community, Please note that our next coreboot leadership meeting is scheduled for Wednesday, August 7,2024.[1] Kindly update the current agenda with matters you wish to see dicussed during the meeting.[2] Thank you. Best regards, Mina Asante. [1](https://www.coreboot.org/calendar.html). [2](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkK…

1 0