commit | 285097c46373211598fac56008a74e1557bd5372 | [log] [tgz] |
---|---|---|
author | Kyösti Mälkki <kyosti.malkki@gmail.com> | Wed Feb 10 17:53:34 2021 +0200 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Apr 21 16:28:25 2021 +0000 |
tree | 26af31430ba9464b1fd62f96d0392beff75dd3aa | |
parent | efece76ed337b6e96281fc54eb27b8c7871a5a10 [diff] |
UPSTREAM: ChromeOS: Use CHROMEOS_NVS guard Replace CONFIG(CHROMEOS) with CONFIG(CHROMEOS_NVS) for cases where the conditional and dependency are clearly about the presence of an ACPI NVS table specified by vendorcode. For couple locations also CONFIG(HAVE_ACPI_TABLES) changes to CONFIG(CHROMEOS_NVS). This also helps find some of the CONFIG(CHROMEOS) cases that might be more FMAP and VPD related and not about ChromeOS per-se, as suggested by followup works. BUG=none BRANCH=none TEST=none Change-Id: I41288e76478be2b41583acf9fcfb38961c8d0f74 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 84d10cc5d38d706ffecd0cd60f6e1f9d90064f96 Original-Change-Id: Ife888ae43093949bb2d3e397565033037396f434 Original-Signed-off-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/50611 Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-by: Angel Pons <th3fanbus@gmail.com> Original-Reviewed-by: Lance Zhao Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/2843708 Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> Commit-Queue: Patrick Georgi <pgeorgi@chromium.org> Tested-by: Patrick Georgi <pgeorgi@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.