GNUBoot
/
coreboot-kgpe-d16
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

board-status: Update the foreword 

There's the sentiment that the Supported_Motherboards wiki page is
outdated. Point out that the list is current (and drop the table of
contents that became a distraction).

Change-Id: Ib2363fad0b7f6951b07b2ad0c85148d9bc729b55
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Reviewed-on: http://review.coreboot.org/12291
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Martin Roth <martinroth@google.com>
This commit is contained in:
Patrick Georgi 2015-11-01 14:18:30 +01:00 committed by Patrick Georgi
parent c1daad2e6f
commit e0e7bba2de
1 changed files with 28 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
util/board_status/to-wiki/foreword.wiki
View File

@ -1,28 +1,39 @@
__NOTOC__
This page was automatically generated. Please do not edit, any edits will be overwritten by an
automatic utility.
= coreboot status by mainboard =
= Mainboards supported by coreboot =
* This list contains reports of successful coreboot execution, ordered by date. It's shows which boards can actually run with current coreboot versions.
This page shows two representations of the same data:
* Using the precise commit id and config.txt, it's possible to reproduce working coreboot builds (assuming no compiler bugs).
First a list of all mainboards supported by coreboot (current within
one hour) ordered by category. For each mainboard the table shows the
latest user-contributed report of a successful boot on the device.
* By sorting it by date, we encourage developers and users to keep ports current and well-tested.
After that, the page provides a time-ordered list of these contributed
reports, with the newest report first.
* Status data comes from the [http://review.coreboot.org/gitweb?p=board-status.git board status repository].
Boards without such reports may boot or there may be some maintenance
required. The reports contain the coreboot configuration and precise commit
id, so it is possible to reproduce the build.
* The coreboot tree [http://review.coreboot.org/gitweb?p=coreboot.git;a=tree;f=util/board_status;hb=HEAD contains a tool] to generate and push suitable data
as well as the scripts that present the data in wiki format.
We encourage developers and users to contribute reports so we know which
devices are well-tested. We have
[http://review.coreboot.org/gitweb?p=coreboot.git;a=tree;f=util/board_status;hb=HEAD a tool in the coreboot repository]
to make contributing easy. The data resides in the
[http://review.coreboot.org/gitweb?p=board-status.git board status repository].
Contributing requires an account on review.coreboot.org
* Board info is automatically generated from Kconfig and board_info.txt files. All boards present in the tree will appear here with varying amount of details.
Sometimes the same board is sold under different names, we've tried to
list all known names but some names might be missing.
* An account on review.coreboot.org is required for sending data.
If the board is not found in the corebootv4's source code, there might
be some form of support that is not ready yet for inclusion in coreboot,
usually people willing to send their patches to coreboot goes through
[http://review.coreboot.org gerrit], so looking there could find some
code for boards that are not yet merged.
* Sometimes the same board is sold under different names, we've tried to list all known names but some names might be missing.
* Some boards have been removed for various reasons, may be brought back if someone works on them. Consult [[Graveyard]] for details.
* If the board is not found in the corebootv4's source code, there might be some form of support that is not ready yet for inclusion in coreboot, usually people willing to send their patches to coreboot goes trough [http://review.coreboot.org gerrit], so looking there could find some code for boards that are not yet merged.
* some vendors have their own coreboot trees/fork, like for instance:
** [http://git.xivo.fr/?p=official/xioh/coreboot.git;a=summary xivo's tree]
** [http://git.chromium.org/gitweb/?p=chromiumos/third_party/coreboot.git;a=summary chrome/chromium's tree]
= Vendor trees =
Some vendors have their own coreboot trees/fork, like for instance:
* [http://git.xivo.fr/?p=official/xioh/coreboot.git;a=summary xivo's tree]
* [http://git.chromium.org/gitweb/?p=chromiumos/third_party/coreboot.git;a=summary chrome/chromium's tree]