| commit | 3f0563eaaa839fcbebcca533afb0d9af041a529b | [log] [tgz] |
|---|---|---|
| author | Yu-Ping Wu <yupingso@chromium.org> | Wed Dec 06 06:59:30 2023 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 02 19:30:52 2024 |
| tree | ff4b102f16f75a0da9e67ff371ea176e136194ba | |
| parent | 7a051af561fa3ba549839b81e850c4cd0b00ad5c [diff] |
soc/mediatek/mt8192: Update dram.elf from 1.6.3 to 1.8.3 To sync DRAMC_PARAM_HEADER_VERSION with CB:61132 and CB:62549, update dram.elf from ChromeOS build 15692.0.0. BUG=b:315082772 (cherry picked from commit 30e541a7d08a6446bd981c1be6378321f2e65594) Original-Change-Id: I2ec5b724cf69892f04eea3c512cb28efafc02031 Original-Signed-off-by: Yu-Ping Wu <yupingso@chromium.org> GitOrigin-RevId: 30e541a7d08a6446bd981c1be6378321f2e65594 Change-Id: I56716be2adf6cb194e85d431651be1cc6da0b752 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/blobs/+/5156849 Reviewed-by: Kshitij Shah <tij@google.com> Tested-by: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> Commit-Queue: Kshitij Shah <tij@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.