coreboot-kgpe-d16/src/vendorcode
Sean Rhodes e3d9b0aa3f vc/intel/raptorlake: Add the FSP v4301.01 headers
Move the existing FSP 4221.00 headers for Raptor Lake to a
subdirectory called 4221.00_google, and select this if the
vendor is Google.

Add the standard FSP 4301.01 headers to a separate directory,
from Intel download #686654, and select this for all other
vendors.

Signed-off-by: Sean Rhodes <sean@starlabs.systems>
Change-Id: Icd99bdee1eeac70dfcaca3d07150d3de6bb83d81
Reviewed-on: https://review.coreboot.org/c/coreboot/+/77101
Reviewed-by: Matt DeVillier <matt.devillier@gmail.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
2023-09-15 13:48:37 +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 vendorcode/eltan/security: update attribute use 2023-09-08 15:22:44 +00:00
google chromeos/cse_board_reset.c: Clear EC AP_IDLE flag 2023-09-14 01:56:09 +00:00
intel vc/intel/raptorlake: Add the FSP v4301.01 headers 2023-09-15 13:48:37 +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.