bb8d069dd3
This change moves pvmfw cbmem implementation to chromeos directory and under CHROMEOS kconfig. The kconfigs have been renamed accordingly and with this change CHROMEOS_PVMFW_CBMEM is enabled by default for CHROMEOS. BUG=b:410735713 TEST=The build with CONFIG_CHROMEOS=y allocates buffer for pvmfw, the depthcharge adds the location and size of the buffer to the kernel command line Change-Id: I024f21ceee1334ebd7ae9bf1b897ad670ddc9ef9 Signed-off-by: Bartłomiej Grzesik <bgrzesik@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/87763 Reviewed-by: Julius Werner <jwerner@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org> |
||
|---|---|---|
| .. | ||
| amd | ||
| cavium | ||
| eltan | ||
| intel | ||
| mediatek | ||
| siemens | ||
| wuffs | ||
| Makefile.mk | ||
| README.md | ||
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.