[coreboot-gerrit] Patch set updated for coreboot: a00676c boardstatus: Add useful info from old page header to foreword.

[Vladimir Serbinenko (phcoder@gmail.com)]

Vladimir Serbinenko (phcoder at gmail.com) just uploaded a new patch set to gerrit, which you can find at http://review.coreboot.org/4743

-gerrit

commit a00676c1f005f45782254c0f19f7c943da8d45c2
Author: Vladimir Serbinenko <phcoder at gmail.com>
Date:   Sun Jan 19 03:50:06 2014 +0100

    boardstatus: Add useful info from old page header to foreword.
    
    Change-Id: Ie3d1be1e51df458cd8b55230c888f032ab705ef8
    Signed-off-by: Vladimir Serbinenko <phcoder at gmail.com>
---
 util/board_status/to-wiki/foreword.wiki | 25 +++++++++++++++++++------
 1 file changed, 19 insertions(+), 6 deletions(-)

diff --git a/util/board_status/to-wiki/foreword.wiki b/util/board_status/to-wiki/foreword.wiki
index ef64daf..be05c8c 100644
--- a/util/board_status/to-wiki/foreword.wiki
+++ b/util/board_status/to-wiki/foreword.wiki
@@ -1,12 +1,25 @@
 = coreboot status by mainboard =
 
-This list contains reports of successful coreboot execution, ordered by date. It's shows which boards can actually run with current coreboot versions.
-Using the precise commit id and config.txt, it's possible to reproduce working coreboot builds (assuming no compiler bugs).
+* This list contains reports of successful coreboot execution, ordered by date. It's shows which boards can actually run with current coreboot versions.
 
-By sorting it by date, we encourage developers and users to keep ports current and well-tested.
+* Using the precise commit id and config.txt, it's possible to reproduce working coreboot builds (assuming no compiler bugs).
 
-Status data comes from the [http://review.coreboot.org/gitweb?p=board-status.git board status repository].
-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
+* By sorting it by date, we encourage developers and users to keep ports current and well-tested.
+
+* Status data comes from the [http://review.coreboot.org/gitweb?p=board-status.git board status repository].
+
+* 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.
 
-An account on review.coreboot.org is required for sending data.
+* 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.
+
+* An account on review.coreboot.org is required for sending data.
+
+* 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]