| commit | 0de4716fa076ca01688826678c5c03d7523cb761 | [log] [tgz] |
|---|---|---|
| author | Nicholas Chin <nic.c3.14@gmail.com> | Thu Sep 22 19:06:42 2022 -0600 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 12 23:11:07 2022 +0000 |
| tree | b19c27b0ed21d2c51b5d4bd3a0449c6b03adc25f | |
| parent | 868080896f2a6913bc381e8e5a391ddd216c4e13 [diff] |
UPSTREAM: Docs/architecture: Fix filename for coreboot architecture diagram A spelling mistake in the markdown reference to the coreboot vs EDK II bootflow diagram was previously fixed, but the actual filename was not changed resulting in a broken reference. (cherry picked from commit c4686419176ccfb1bf4bcb94fb25c040e05714fd) Original-Change-Id: I512646e9af312ba2e1db8f597f6fffa8d54a3515 Original-Signed-off-by: Nicholas Chin <nic.c3.14@gmail.com> Original-Reviewed-on: https://review.coreboot.org/c/coreboot/+/67782 Original-Reviewed-by: Elyes Haouas <ehaouas@noos.fr> Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Felix Singer <felixsinger@posteo.net> GitOrigin-RevId: c4686419176ccfb1bf4bcb94fb25c040e05714fd Change-Id: I6b0c86425a41650350a7a97a4f8e805896550f44 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/3941946 Commit-Queue: Rob Barnes <robbarnes@google.com> Reviewed-by: Rob Barnes <robbarnes@google.com> Tested-by: Rob Barnes <robbarnes@google.com> Reviewed-by: Paul Fagerburg <pfagerburg@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.