| commit | 7ec4671f81c3a5fab33950f8635912f1a549323e | [log] [tgz] |
|---|---|---|
| author | Jakub Czapiga <jacz@semihalf.com> | Tue Oct 25 15:20:03 2022 +0000 |
| committer | Yu-Ping Wu <yupingso@google.com> | Thu Oct 27 04:34:25 2022 +0000 |
| tree | 632634fd8ffde7eca486d8c0ecd60482c0dc3741 | |
| parent | 9e4488ab06fd9c434a958cfcc5bfd7893a64e1a6 [diff] |
Update vboot submodule to upstream main Updating from commit id b827ddb9: 2022-09-01 06:37:33 +0000 - (tests: Ensure auxfw sync runs after EC sync) to commit id 148e5b83: 2022-10-25 09:36:59 +0000 - (Makefile: Fix and simplify the RUNTEST test wrapper) This brings in 28 new commits: 148e5b83 Makefile: Fix and simplify the RUNTEST test wrapper a9c47c41 futility/cmd_show: set uninitialized variable e18a6cda gscvd: presume GBB flags are zero when hashing the RO space contents 0b0aee9c gscvd: refactor discovering GBB in the image ff1749cb futility: add option to save ro_gscvd section in a blob 84c65cd3 vboot_reference: Check OS/firmware mismatch and report to UMA 9a1be550 cmd_update: avoid variable name aliasing d0f7fdf6 treewide: Fix copyrights and extra new lines at end of file 0ca75fd1 tpm_lite: Fix copyrights, line endings, extra new lines at end of file 4ca43a34 crossystem: arm: Retry if we fail to read a GPIO f1a7efc0 futility: updater: Scan patch files for the signer_config manifest 64803227 futility: updater: Support patching GSCVD 2aa69d0c futility: Remove validate_rec_mrc command 0ca7a9e4 firmware: host: futility: Add CBFS metadata hash support aaeb307f futility: Use ccd update mode for suzyq ti50 aa44b7cf vboot: gbb_flags_common should treat ccd_ti50 like ccd_cr50 ff8bb2d9 futility: Address double free 6a33a0fc treewide: Fix license headers to conform with linter b2b4f767 DIR_METADATA: Add V2 Test Plans. 5346938c futility gscvd: add option to print out root key hash 5790c0aa gscvd: add support for reading ranges from the image 499e5743 gbb_flags_common.sh: Restore tmpfile cleanup trap f3f9d2a6 scripts/OWNERS: Fix engeg email chromium -> google ce620761 tests: Remove --allow-multiple-definition linker option 956c2efb futility: Skip picking apart an x86 kernel if has the EFI stub 9f2e9804 Avoid build failures on recent distros 62cc7885 subprocess: Log subprocess arguments when running 3bd35108 2api: Add a new entry point for only loading and verifying the kernel Signed-off-by: Jakub Czapiga <jacz@semihalf.com> Change-Id: I9a16d6e02cee34140ec375ed6166f47560459140 Reviewed-on: https://review.coreboot.org/c/coreboot/+/68540 Reviewed-by: Julius Werner <jwerner@chromium.org> Reviewed-by: Yu-Ping Wu <yupingso@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.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.