| commit | 6e9016d7f69d535db63b167676b744059d2c2cb8 | [log] [tgz] |
|---|---|---|
| author | Mathew King <mathewk@chromium.org> | Thu Mar 21 12:50:54 2019 -0600 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Mar 26 04:43:48 2019 -0700 |
| tree | 15ab5bb6aefafd3966044a0d15c3ffcbef0cd0da | |
| parent | c88b64f2d347946115381c2beb7439770ee891af [diff] |
UPSTREAM: grunt: Mark RW_LEGACY as CBFS Depthcharge is changing how the RW_LEGACY CBFS is handled for alternate bootloaders, see https://crrev.com/c/1528550 and https://crrev.com/c/1530303. This means that RW_LEGACY must be marked as CBFS in the fmap in order to work. All boards except for kahlee(grunt) have CBFS marked. BUG=b:128703316 TEST=Build and ran on grunt along with chromium patches on grunt and was able to list alternate bootloader with ctrl+l BRANCH=none Change-Id: I618b40957ff3b82a0f93b9b58c9d8331ea1859af Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: b08906b2406bf93cae692a8ac5bc75302038a4c2 Original-Change-Id: I843d565a9503d27e666a34e59aba263ec490c81f Original-Signed-off-by: Mathew King <mathewk@chromium.org> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/32019 Original-Reviewed-by: Martin Roth <martinroth@google.com> Original-Reviewed-by: Patrick Georgi <pgeorgi@google.com> Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-on: https://chromium-review.googlesource.com/1534602 Commit-Ready: Patrick Georgi <patrick@georgi-clan.de> Tested-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-by: Mathew King <mathewk@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.