[U-Boot] [PATCH] Add clarifications to the x86 README

[Stoppa, Igor]

Explicitly list the targets supported in each section of the
instructions
from the x86 README.
---
doc/README.x86 | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)

diff --git a/doc/README.x86 b/doc/README.x86
index af2459c..1105afe 100644
--- a/doc/README.x86
+++ b/doc/README.x86
@@ -19,14 +19,15 @@ work with minimal adjustments on other x86 boards
since coreboot deals with
most of the low-level details.

U-Boot also supports booting directly from x86 reset vector without
coreboot,
-aka raw support or bare support. Currently Link, QEMU x86 targets and
all
-Intel boards support running U-Boot 'bare metal'.
+aka raw support or bare support. U-Boot becomes a replacement for the
BIOS.
+Currently Link, QEMU x86 targets and all Intel boards support running
U-Boot
+'bare metal'.

As for loading an OS, U-Boot supports directly booting a 32-bit or
64-bit
Linux kernel as part of a FIT image. It also supports a compressed
zImage.

-Build Instructions
-------------------
+Build Instructions for U-Boot as coreboot payload
+-------------------------------------------------
Building U-Boot as a coreboot payload is just like building U-Boot for
targets
on other architectures, like below:

@@ -48,6 +49,8 @@ Change the 'Board configuration file' and 'Board
Device Tree Source (dts) file'
to point to a new board. You can also change the Cache-As-RAM (CAR)
related
settings here if the default values do not fit your new board.

+Build Instructions for U-Boot as BIOS replacement (raw/bare mode)
+-----------------------------------------------------------------
Building a ROM version of U-Boot (hereafter referred to as u-boot.rom)
is a
little bit tricky, as generally it requires several binary blobs which
are not
shipped in the U-Boot source tree. Due to this reason, the u-boot.rom
build is
@@ -87,7 +90,7 @@ Now you can build U-Boot and obtain u-boot.rom:
$ make chromebook_link_defconfig
$ make all

-Intel Crown Bay specific instructions:
+Intel Crown Bay specific instructions (raw mode):

U-Boot support of Intel Crown Bay board [4] relies on a binary blob
called
Firmware Support Package [5] to perform all the necessary
initialization steps
@@ -122,7 +125,7 @@ Now you can build U-Boot and obtain u-boot.rom
$ make crownbay_defconfig
$ make all

-Intel Minnowboard Max instructions:
+Intel Minnowboard Max instructions (raw mode):

This uses as FSP as with Crown Bay, except it is for the Atom E3800 series.
Download this and get the .fd file (BAYTRAIL_FSP_GOLD_003_16-SEP-2014.fd at
@@ -189,7 +192,7 @@ Offset   Description         Controlling config
Overall ROM image size is controlled by CONFIG_ROM_SIZE.


-Intel Galileo instructions:
+Intel Galileo instructions (raw mode):

Only one binary blob is needed for Remote Management Unit (RMU) within Intel
Quark SoC. Not like FSP, U-Boot does not call into the binary. The binary is
--
2.1.4