commit | 5349dd14d6a65bac8c3244f1e0903f3724d7d5ed | [log] [tgz] |
---|---|---|
author | Martin Kepplinger <martink@posteo.de> | Thu Feb 07 07:34:46 2019 +0100 |
committer | Patrick Georgi <pgeorgi@google.com> | Mon Feb 11 12:22:38 2019 +0000 |
tree | 22fc071dd883701e24c735f758488085863f7f27 | |
parent | cf39eea2f82c6ab291411a0aa473d01afe0078e2 [diff] |
Documentation: remove the upcoming events chapter from the conferences page I think our docs inside of the codebase might not be the ideal place to announce future events. First, they might be scheduled so shortly before the conference that the change, if at all done, would barely make it to the repo and the web. Also, _if_ really maintained, it would churn the docs unnessesarily. But, I doubt that anyone of us would want to maintain this here at all. Lastly, I think that nobody out there would _look for_ upcoming events in coreboot's documentation. We have bigger problems in the Documentation directory than this :) Change-Id: I918e17a427405a05722c6e0d61dc422f94cac809 Signed-off-by: Martin Kepplinger <martink@posteo.de> Reviewed-on: https://review.coreboot.org/c/31266 Reviewed-by: Philipp Deppenwiese <zaolin.daisuki@gmail.com> Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-by: Angel Pons <th3fanbus@gmail.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.