Newer microcode for family 6, model 0x37, stepping 8 can be found in the intel-microcode repo. Only stepping 3, which is presumable a pre-release model remains in 3rdparty/blobs. Change-Id: I619407f64076d7bacbaaa2f03e3875cdd05139e0 Signed-off-by: Arthur Heymans <email@example.com>
|1 month ago|
|cpu||9 months ago|
|mainboard||3 months ago|
|northbridge||1 year ago|
|pi/amd||2 years ago|
|soc||1 month ago|
|southbridge/amd||2 years ago|
|README.md||3 months ago|
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
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.