| commit | 3a55506618ffbb2c2b72646416bfe1d225d38587 | [log] [tgz] |
|---|---|---|
| author | Marco Chen <marcochen@chromium.org> | Fri Jun 21 20:27:59 2019 +0800 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Feb 24 01:55:40 2021 +0000 |
| tree | 50ba6e484fcdd805cc87532d83bfefbed094f812 | |
| parent | 034eeb8dd5f6d218b9483eb50e33e7ba5027ee76 [diff] |
CHROMIUM: vendorcode/google: load sar config from CBFS first then VPD [ Brian: Based on upstream work that may get refactored: https://review.coreboot.org/c/coreboot/+/33661/1 In ToT, we want to drop VPD support. But for old firmware branches, we may still need to fix up bad VPD. Conflicts: src/vendorcode/google/chromeos/sar.c CONFIG(WIFI_SAR_CBFS) vs. IS_ENABLED(CONFIG_WIFI_SAR_CBFS) ] SAR config provisioned in RO VPD can be done in the factory only. Once it is wrong, we can override the SAR config by updating FW RW which can carry new SAR config in CBFS. As a result, we should check CBFS first then VPD. BUG=b:173465272 TEST=none Change-Id: I5aa6235fb7a6d0b2ed52893a42f7bd57806af6c1 Signed-off-by: Marco Chen <marcochen@chromium.org> Signed-off-by: Brian Norris <briannorris@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/2715888 Reviewed-by: Furquan Shaikh <furquan@chromium.org>
coreboot is a Free Software project aimed at replacing the proprietary BIOS (firmware) found in most computers. coreboot performs a little bit of hardware initialization and then executes additional boot logic, called a payload.
With the separation of hardware initialization and later boot logic, coreboot can scale from specialized applications that run directly firmware, run operating systems in flash, load custom bootloaders, or implement firmware standards, like PC BIOS services or UEFI. This allows for systems to only include the features necessary in the target application, reducing the amount of code and flash space required.
coreboot was formerly known as LinuxBIOS.
After the basic initialization of the hardware has been performed, any desired “payload” can be started by coreboot.
See https://www.coreboot.org/Payloads for a list of supported payloads.
coreboot supports a wide range of chipsets, devices, and mainboards.
For details please consult:
ANY_TOOLCHAIN Kconfig option if you’re feeling lucky (no support in this case).Optional:
make menuconfig and make nconfig)Please consult https://www.coreboot.org/Build_HOWTO for details.
If you want to test coreboot without any risks before you really decide to use it on your hardware, you can use the QEMU system emulator to run coreboot virtually in QEMU.
Please see https://www.coreboot.org/QEMU for details.
Further details on the project, a FAQ, many HOWTOs, news, development guidelines and more can be found on the coreboot website:
You can contact us directly on the coreboot mailing list:
https://www.coreboot.org/Mailinglist
The copyright on coreboot is owned by quite a large number of individual developers and companies. Please check the individual source files for details.
coreboot is licensed under the terms of the GNU General Public License (GPL). Some files are licensed under the “GPL (version 2, or any later version)”, and some files are licensed under the “GPL, version 2”. For some parts, which were derived from other projects, other (GPL-compatible) licenses may apply. Please check the individual source files for details.
This makes the resulting coreboot images licensed under the GPL, version 2.