coreboot/src/vendorcode
Eric Lai 8cb2f185d1 vc/google/chromeos: use fw_config field to return sar filename
Use fw_config field to return sar filename instead of fw_config probe.
Return filename unconditionly because the sar_id must be valid in
CBI. If invalid sar_id, the file won't exist in CBFS by design.

Signed-off-by: Eric Lai <eric_lai@quanta.corp-partner.google.com>
Change-Id: I7b75c5d4fd3c459ad7232bb16c6218a6218f1f77
Reviewed-on: https://review.coreboot.org/c/coreboot/+/70896
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Julius Werner <jwerner@chromium.org>
Reviewed-by: Subrata Banik <subratabanik@google.com>
Reviewed-by: Ivy Jian <ivy.jian@quanta.corp-partner.google.com>
2022-12-24 05:50:13 +00:00
..
amd vc/amd,soc/amd/mendocino: Add SVC_CMD_GET_PREV_BOOT_STATUS 2022-12-21 13:36:25 +00:00
cavium vc/cavium/bdk/libbdk-arch/bdk-numa.c: Fix old-style function definition 2022-12-06 16:18:59 +00:00
eltan vc/eltan/security/mboot/Makefile.inc: Remove path to non-existent folder 2022-12-13 15:19:58 +00:00
google vc/google/chromeos: use fw_config field to return sar filename 2022-12-24 05:50:13 +00:00
intel vc/intel/fsp/mtl: Update header files from 2404_00 to 2431_80 2022-12-14 06:47:47 +00:00
mediatek vc/mediatek/mt8195/Makefile.inc: Remove path to non-existent folder 2022-12-12 01:30:26 +00:00
siemens cbfs: Simplify load/map API names, remove type arguments 2020-12-02 22:13:17 +00:00
Makefile.inc soc/mediatek/mt8192: initialize DRAM using vendor reference code 2021-03-08 03:15:43 +00:00
README.md src/vendorcode: Add a README.md file 2022-10-20 14:52:41 +00:00

The files in the coreboot src/vendorcode subdirectory are supplied by various hardware and software vendors to support their platforms. While these directories and files are a part of the coreboot project, their licenses, coding styles, and maintenance may be significantly different than the rest of the coreboot codebase.

By contributing these directories and files to the coreboot codebase, the authors and copyright holders have agreed to the use and modification of these files by the coreboot community, however the final ownership and responsibility still remains with the company that contributed the files.

The ideal goal would be to properly integrate these files into coreboot proper. But such undertakings should be coordinated with the owners. Community modification should in general be limited to fixing issues and adding functionality.

Licenses for the files were determined by the copyright holder when the files were contributed. All files here must have an open source license compatible with coreboot's GPL v2.