| commit | 9e53f5ecdc1a43c507bba004cfda2f17d166e52d | [log] [tgz] |
|---|---|---|
| author | Sean Rhodes <sean@starlabs.systems> | Thu Aug 10 09:19:34 2023 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 17 02:50:04 2023 |
| tree | 767a4dca0e7513e0e9507eb0e81c496023e5856e | |
| parent | 92a989925e3855e6602334b47ad95cfc65c5f763 [diff] |
mb/starlabs/starbook: Consolidate version history From mid-2022, EC updates were bundled into coreboot using the ITE mirror protocol, leading to individual binaries being added solely to the blobs repo. This made separate version histories redundant. To simplify tracking, the old history has been removed, centralizing all changes in the blobs repository. (cherry picked from commit 542c27d48714ad4174f5b3ea47659f0fca3cdaf2) Original-Signed-off-by: Sean Rhodes <sean@starlabs.systems> Original-Change-Id: Icdac82a0dfd90559a9a7d9808b3fb57a164d121f GitOrigin-RevId: 542c27d48714ad4174f5b3ea47659f0fca3cdaf2 Change-Id: I4a518b1aa651e1bdaed8eac08835b548eb67ae42 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/blobs/+/4780417 Commit-Queue: Jonathon Murphy <jpmurphy@google.com> Tested-by: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> Reviewed-by: Jonathon Murphy <jpmurphy@google.com>
While coreboot attempts to be binary free, some coreboot mainboards require vendor binaries to support silicon and features. It is an unfortunate fact, as silicon has become more complicated, vendors are using more binaries to support their silicon. The coreboot community can not control the vendors, nor completely eliminate binaries, but it can set standards and expectations for vendor participation. coreboot needs policies and guidelines to meet GPL licence requirements and to organize and maintain standards within coreboot.
To accept binaries in coreboot 3rdparty/blobs repository, the binary must meet the following:
In case of non-ISA binary, documented usage conventions are required
Examples:
The binary must be accompanied by a distribution license. The license must allow unlimited redistribution to allow coreboot contributors to create coreboot images for third parties which contain this and other blobs.
Source code linked into coreboot may not be committed to the binary repository. Such source code and header files must be committed to the coreboot repository instead.
The binary must contain the version and how to extract the version must be published in the ABI
Each binary release must be accompanied by a release note that contains all of the following (if a field is unknown or unavailable, mark it as unknown or N/A):
* version * release date * supported silicon * instructions, requirements, and dependencies * changes since the last version * errata, known issues * toolchain version(s), if applicable * ABI version and link to the published ABI (in the binary repository)
The commit message should summarize the release note and contain any additional information that might be specific to coreboot. It is helpful to indicate how the binary was tested within coreboot and list any known exceptions or errata.