coreboot/src/vendorcode
Nick Vaccaro 55606625bb vc/intel/raptorlake: Use FSP v4301.01 headers for Google
Remove the existing FSP 4221.00 headers subdirectory called
4221.00_google, and have Google vendor devices use FSP 4301.01.

BUG=b:306181828
TEST=`emerge-brya coreboot chromeos-bootimage`, flash and boot skolas to kernel.

Change-Id: Ic64b3aec62f0d6302278393bf06d090f43c0d592
Signed-off-by: Nick Vaccaro <nvaccaro@google.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/78444
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: <srinivas.kulkarni@intel.com>
Reviewed-by: Bora Guvendik <bora.guvendik@intel.com>
Reviewed-by: Subrata Banik <subratabanik@google.com>
2023-10-19 04:50:26 +00:00
..
amd vc/amd/pi: Add SPDX headers to all files that don't have them 2023-08-26 21:38:58 +00:00
cavium vendorcode/cavium: Use C99 flexible arrays 2023-08-08 16:01:08 +00:00
eltan treewide: convert to tpm_result_t 2023-09-28 16:54:37 +00:00
google treewide: convert to tpm_result_t 2023-09-28 16:54:37 +00:00
intel vc/intel/raptorlake: Use FSP v4301.01 headers for Google 2023-10-19 04:50:26 +00:00
mediatek vendorcode/mediatek/mt8195: Fix set but unused variables 2023-05-13 17:19:53 +00:00
siemens vc/siemens: Only add the include path for hwlib when needed 2023-08-26 21:13:50 +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.