1
0
Fork
You've already forked coreboot
0
  • C 93.9%
  • ASL 2.3%
  • Makefile 1%
  • Pawn 0.5%
  • Go 0.4%
  • Other 1.8%
Julius Werner 8f34fdfab3 Remove <swab.h> and swabXX() functions 
GCC generates correct code for __builtin_bswapXX() on all architectures,
including ArmV4. It seems that whatever bug caused this to not work back
in commit 879ea7fce8 ("endian: Replace explicit byte swapping with
compiler builtin") has been fixed now. We can eliminate the swabXX()
functions and simplify the code.
All instances that had been calling these functions directly should have
been using real endianness conversions anyway.
Change-Id: I19713fd009aa5c0e01c4a42e0cf012364d6bed60
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/90438
Reviewed-by: Maximilian Brune <maximilian.brune@9elements.com>
Reviewed-by: Yu-Ping Wu <yupingso@google.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Frans Hendriks <fhendriks@eltan.com>
2025年12月12日 07:09:45 +00:00
3rdparty 3rdparty/blobs: Update to upstream main 2025年12月09日 22:27:32 +00:00
configs config/builder/mitac: Hook up public FSP repo and microcode 2025年08月30日 13:56:13 +00:00
Documentation drivers/option/cfr: Remove old sm_object from constructor 2025年11月15日 15:27:32 +00:00
LICENSES LICENSES: Add LGPL 2.1 license 2024年02月18日 01:56:38 +00:00
payloads Remove <swab.h> and swabXX() functions 2025年12月12日 07:09:45 +00:00
spd spd/ddr4: Add three more parts 2025年12月02日 01:54:30 +00:00
src Remove <swab.h> and swabXX() functions 2025年12月12日 07:09:45 +00:00
tests tests/imd: Fix invalid NULL comparison on uintptr_t 2025年09月30日 11:55:53 +00:00
util util/ifdtool: fix typo PSL->MSL 2025年12月03日 16:55:30 +00:00
.checkpatch.conf .checkpatch.conf: Set max line length to 96 2024年12月04日 07:36:22 +00:00
.clang-format Treewide: Fix incorrect SPDX license strings 2024年02月18日 01:55:57 +00:00
.editorconfig .editorconfig: Add indent style & size of 2 spaces for shell 2023年12月20日 22:30:33 +00:00
.gitignore .gitignore: Add .clangd as a "Development friendly file" 2025年10月24日 21:35:19 +00:00
.gitmodules .gitmodules: Ignore changes make by what-jenkins-does 2025年07月17日 20:38:35 +00:00
.gitreview .gitreview: Update default branch from master to main 2023年12月23日 16:44:31 +00:00
.mailmap .mailmap: Add a .mailmap file for git 2022年03月08日 18:53:47 +00:00
AUTHORS AUTHORS: Update list to 25.03 2025年05月08日 22:32:29 +00:00
COPYING update license template. 2006年08月12日 22:03:36 +00:00
gnat.adc drivers/intel/gma: Allow SPARK function with side effects 2024年03月01日 18:46:30 +00:00
MAINTAINERS MAINTAINERS: Add Chen-Tsung Hsieh for MediaTek platforms 2025年11月01日 07:23:26 +00:00
Makefile Reland "tests: Allow specifying vboot source directory" 2025年09月16日 15:04:07 +00:00
Makefile.mk soc/intel/common/block/rtc/rtc.c: Top Swap: add Slot B selection mechanism 2025年12月04日 01:31:25 +00:00
README.md Documentation: Update internal URL's 2024年01月04日 14:22:51 +00:00
toolchain.mk tree: Replace scan-build by clang-tidy 2025年07月01日 01:12:32 +00:00

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:

https://www.coreboot.org

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, .apcb files containing configuration parameters for AMD firmware binaries, and 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.