f49f3e6aa4
Updating from commit id 034907b2: 2023-06-03 08:10:11 +0000 - (vboot_reference: eliminate redundant call to write protect EC-RO) to commit id 0c11187c: 2023-08-07 11:41:45 +0000 - (vboot_reference: Rename Cr50 to GSC when applicable) This brings in 38 new commits: 0c11187c vboot_reference: Rename Cr50 to GSC when applicable 76c160e2 futility: updater: Support --unlock_me with --mode=output 48a12071 futility: Add `show` test for CBFS integration firmware b419912f futility: Pull file names into ft_show_bios() subtypes db56d9c5 futility: Clarify `name` and remove `data` argument of file type funcs 311f59e8 futility: Use -P for signing tests 854c71b9 tests: futility: Make test_show_contents easier to update 5f5a695e futility: Document machine parseable format guidelines 774c700f futility: Fix HWID digest footer output 8cc8b710 futility: Fix build with a single RW partition and CBFS verification 6d4b03e5 futility/cmd_read.c: Implement --split-path|-s switch 636d5b16 Correct a malloc() check in VbExStreamOpen() def2f5af firmware/2lib: Switch to RO immediately if only one slot present 9c9931b4 futility/cmd_read.c: Optimise to limit SPI transaction cb56129f checkpatch: Change max line length from 80 to 96 aa23241a tests: Fix run_vbutil_kernel_arg_tests.sh d7c26f52 futility: Follow-up fixes to CL:4548417 56490778 futility: add machine friendly print option 23e750b8 tests: Remove duplicate test for vb2api_fail() 612d140b futility: updater: fix custom label devices using customization_id 69cbe7ee Revert "futility: Avoid unnecessary servo control command" 290b72d6 vbutil_kernel: Drop alignment check for EFI stub 5d582eb5 sign_android_image.sh: Preserve capabilities for EROFS as well 8c30aaab futility: Avoid unnecessary servo control command 58f8bb5c futility: Fix flash teardown issue 2d9f9cdb sign_official_build: add cloud-signing param d0ceeee6 image_signing: sign_official_build: create a proper main() func 38cfb9b0 Revert "make_dev_ssd.sh: Add support for kdump" 2c43e4dd .clang-format: Change the ColumnLimit from 80 to 96 3107ce77 host/lib/flashrom_drv.c: Check chip len symmetrically across R/W ops 0549e3c1 2load_kernel: Change bootloader_address out-parameter to offset 979f61de Make sign_android_image.sh support EROFS image format as well. bb5ccd7d lib/flashrom_drv.c: Pass regions as pointer + size. 249a3477 vbutil_kernel: Move kernel's EFI boot stub into bootloader section c8998d5f host/lib: Use absolute path for flashrom 564d9274 futility/updater_utils.c: Drop flashrom cli producer 9bf3edf8 futility/updater.c: Clarify conditions of do_update 212643bd futility/updater.c: Use canonical defines Change-Id: I0947f0f6670328b779d2a8ef240ca196ef615cec Signed-off-by: Yu-Ping Wu <yupingso@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/77086 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Yidi Lin <yidilin@google.com> |
||
|---|---|---|
| 3rdparty | ||
| Documentation | ||
| LICENSES | ||
| configs | ||
| payloads | ||
| spd | ||
| src | ||
| tests | ||
| util | ||
| .checkpatch.conf | ||
| .clang-format | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmodules | ||
| .gitreview | ||
| .mailmap | ||
| AUTHORS | ||
| COPYING | ||
| MAINTAINERS | ||
| Makefile | ||
| Makefile.inc | ||
| README.md | ||
| gnat.adc | ||
| toolchain.inc | ||
README.md
coreboot README
coreboot is a Free Software project aimed at replacing the proprietary firmware (BIOS/UEFI) found in most computers. coreboot performs the required hardware initialization to configure the system, then passes control to a different executable, referred to in coreboot as the payload. Most often, the primary function of the payload is to boot the operating system (OS).
With the separation of hardware initialization and later boot logic, coreboot is perfect for a wide variety of situations. It can be used for specialized applications that run directly in the firmware, running operating systems from flash, loading custom bootloaders, or implementing firmware standards, like PC BIOS services or UEFI. This flexibility allows coreboot systems to include only the features necessary in the target application, reducing the amount of code and flash space required.
Source code
All source code for coreboot is stored in git. It is downloaded with the command:
git clone https://review.coreboot.org/coreboot.git.
Code reviews are done in the project's Gerrit instance.
The code may be browsed via coreboot's Gitiles instance.
The coreboot project also maintains a mirror of the project on github. This is read-only, as coreboot does not accept github pull requests, but allows browsing and downloading the coreboot source.
Payloads
After the basic initialization of the hardware has been performed, any desired "payload" can be started by coreboot.
See https://doc.coreboot.org/payloads.html for a list of some of coreboot's supported payloads.
Supported Hardware
The coreboot project supports a wide range of architectures, chipsets, devices, and mainboards. While not all of these are documented, you can find some information in the Architecture-specific documentation or the SOC-specific documentation.
For details about the specific mainboard devices that coreboot supports, please consult the Mainboard-specific documentation or the Board Status pages.
Releases
Releases are currently done by coreboot every quarter. The release archives contain the entire coreboot codebase from the time of the release, along with any external submodules. The submodules containing binaries are separated from the general release archives. All of the packages required to build the coreboot toolchains are also kept at coreboot.org in case the websites change, or those specific packages become unavailable in the future.
All releases are available on the coreboot download page.
Please note that the coreboot releases are best considered as snapshots of the codebase, and do not currently guarantee any sort of extra stability.
Build Requirements and building coreboot
The coreboot build, associated utilities and payloads require many additional tools and packages to build. The actual coreboot binary is typically built using a coreboot-controlled toolchain to provide reproducibility across various platforms. It is also possible, though not recommended, to make it directly with your system toolchain. Operating systems and distributions come with an unknown variety of system tools and utilities installed. Because of this, it isn't reasonable to list all the required packages to do a build, but the documentation lists the requirements for a few different Linux distributions.
To see the list of tools and libraries, along with a list of instructions to get started building coreboot, go to the Starting from scratch tutorial page.
That same page goes through how to use QEMU to boot the build and see the output.
Website and Mailing List
Further details on the project, as well as links to documentation and more can be found on the coreboot website:
You can contact us directly on the coreboot mailing list:
https://doc.coreboot.org/community/forums.html
Copyrights and Licenses
Uncopyrightable files
There are many files in the coreboot tree that we feel are not copyrightable due to a lack of creative content.
"In order to qualify for copyright protection in the United States, a work must satisfy the originality requirement, which has two parts. The work must have “at least a modicum” of creativity, and it must be the independent creation of its author."
https://guides.lib.umich.edu/copyrightbasics/copyrightability
Similar terms apply to other locations.
These uncopyrightable files include:
- Empty files or files with only a comment explaining their existence. These may be required to exist as part of the build process but are not needed for the particular project.
- Configuration files either in binary or text form. Examples would be files such as .vbt files describing graphics configuration, spd files as binary .spd or text *spd*.hex representing memory chip configuration.
- Machine-generated files containing version numbers, dates, hash values or other "non-creative" content.
As non-creative content, these files are in the public domain by default. As such, the coreboot project excludes them from the project's general license even though they may be included in a final binary.
If there are questions or concerns about this policy, please get in touch with the coreboot project via the mailing list.
Copyrights
The copyright on coreboot is owned by quite a large number of individual developers and companies. A list of companies and individuals with known copyright claims is present at the top level of the coreboot source tree in the 'AUTHORS' file. Please check the git history of each of the source files for details.
Licenses
Because of the way coreboot began, using a significant amount of source code from the Linux kernel, it's licensed the same way as the Linux Kernel, with GNU General Public License (GPL) Version 2. Individual files are licensed under various licenses, though all are compatible with GPLv2. The resulting coreboot image is licensed under the GPL, version 2. All source files should have an SPDX license identifier at the top for clarification.
Files under coreboot/Documentation/ are licensed under CC-BY 4.0 terms. As an exception, files under Documentation/ with a history older than 2017-05-24 might be under different licenses.
Files in the coreboot/src/commonlib/bsd directory are all licensed with the BSD-3-clause license. Many are also dual-licensed GPL-2.0-only or GPL-2.0-or-later. These files are intended to be shared with libpayload or other BSD licensed projects.
The libpayload project contained in coreboot/payloads/libpayload may be licensed as BSD or GPL, depending on the code pulled in during the build process. All GPL source code should be excluded unless the Kconfig option to include it is set.
The Software Freedom Conservancy
Since 2017, coreboot has been a member of The Software Freedom Conservancy, a nonprofit organization devoted to ethical technology and driving initiatives to make technology more inclusive. The conservancy acts as coreboot's fiscal sponsor and legal advisor.