Remove trailing whitespace in files that aren't typically checked. Signed-off-by: Martin Roth <email@example.com> Change-Id: I8dfffbdeaadfa694fef0404719643803df601065 Reviewed-on: https://review.coreboot.org/c/coreboot/+/50704 Tested-by: build bot (Jenkins) <firstname.lastname@example.org> Reviewed-by: Angel Pons <email@example.com>
|6 months ago|
|3rdparty||6 months ago|
|Documentation||6 months ago|
|LICENSES||6 months ago|
|configs||6 months ago|
|payloads||6 months ago|
|src||6 months ago|
|tests||6 months ago|
|util||6 months ago|
|.checkpatch.conf||3 years ago|
|.clang-format||2 years ago|
|.editorconfig||2 years ago|
|.gitignore||9 months ago|
|.gitmodules||10 months ago|
|.gitreview||9 years ago|
|AUTHORS||1 year ago|
|COPYING||15 years ago|
|MAINTAINERS||6 months ago|
|Makefile||7 months ago|
|Makefile.inc||6 months ago|
|README.md||2 years ago|
|gnat.adc||1 year ago|
|toolchain.inc||1 year ago|
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
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
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:
- gcc / g++
Because Linux distribution compilers tend to use lots of patches. coreboot
does lots of "unusual" things in its build system, some of which break due
to those patches, sometimes by gcc aborting, sometimes - and that's worse -
by generating broken object code.
Two options: use our toolchain (eg. make crosstools-i386) or enable the
ANY_TOOLCHAINKconfig option if you're feeling lucky (no support in this
- iasl (for targets with ACPI support)
- libssl-dev (openssl)
- doxygen (for generating/viewing documentation)
- gdb (for better debugging facilities on some targets)
- ncurses (for
- flex and bison (for regenerating parsers)
Please consult https://www.coreboot.org/Build_HOWTO for details.
Testing coreboot Without Modifying Your Hardware
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.
Website and Mailing List
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:
Copyright and License
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.