| commit | 68fa266c224756a19a638857b82d9042b121bcef | [log] [tgz] |
|---|---|---|
| author | Kangheui Won <khwon@chromium.org> | Wed Oct 07 14:29:38 2020 +1100 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Oct 21 18:11:05 2020 +0000 |
| tree | 3eca0061d444df15f1a3fdc360bfc7e50fe6ae6f | |
| parent | 5a64591022b69da80028c2ed5c636216dfef0025 [diff] |
UPSTREAM: rules.h: change verstage name if it starts before bootblock VBOOT_STARTS_VEFORE_BOOTBLOCK indicates that verstage starts before bootblock. However "cbmem -1" will first try to match "bootblock starting" to find out the beginning of console for current boot. Change ENV_STRING for verstage to "verstage-before-bootblock" in the case and add regex in cbmem utility to grab it. BUG=b:159220781 TEST=flash and boot, check `cbmem -1` BRANCH=zork Signed-off-by: Martin Roth <gaumless@gmail.com> Original-Commit-Id: 4b5c8b554154f290d509b6db3c44f850134581b7 Original-Signed-off-by: Kangheui Won <khwon@chromium.org> Original-Change-Id: Ica38f6bfeb05605caadac208e790fd072b352732 Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/46060 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Martin Roth <martinroth@google.com> Original-Reviewed-by: Julius Werner <jwerner@chromium.org> Original-Reviewed-by: Edward O'Callaghan <quasisec@chromium.org> Change-Id: I6c28089acf025fc4c6420a0f5d72e1900752d3fd Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/2458818 Reviewed-by: Martin Roth <martinroth@google.com> Commit-Queue: Martin Roth <martinroth@google.com> Tested-by: Martin Roth <martinroth@google.com> (cherry picked from commit eb9a894107a39bfb0b3b5692b5cd36e6731800d7) Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/2490641 Auto-Submit: Martin Roth <martinroth@google.com>
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.