summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2015-02-04 16:26:14 +0800
committerSimon Glass <sjg@chromium.org>2015-02-06 12:07:46 -0700
commit67582c00d788c150bb717671f988f234bd73ce5e (patch)
treec0f282f93bd56d3de34554c49348056504fbe06c
parent6df7ffea1399de57e5b3be6e3cd0986869087663 (diff)
downloadu-boot-imx-67582c00d788c150bb717671f988f234bd73ce5e.zip
u-boot-imx-67582c00d788c150bb717671f988f234bd73ce5e.tar.gz
u-boot-imx-67582c00d788c150bb717671f988f234bd73ce5e.tar.bz2
x86: Add Intel Galileo instructions in README.x86
Add some instructions about building U-Boot for Intel Galileo board. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org>
-rw-r--r--doc/README.x8624
1 files changed, 20 insertions, 4 deletions
diff --git a/doc/README.x86 b/doc/README.x86
index c699b79..fb87682 100644
--- a/doc/README.x86
+++ b/doc/README.x86
@@ -18,8 +18,8 @@ U-Boot supports running as a coreboot [1] payload on x86. So far only Link
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, Intel Crown Bay and Intel
-Minnowboard Max support running U-Boot 'bare metal'.
+aka raw support or bare support. Currently Link, Intel Crown Bay, Intel
+Minnowboard Max and Intel Galileo 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.
@@ -110,7 +110,6 @@ Now you can build U-Boot and obtain u-boot.rom
$ make crownbay_defconfig
$ make all
-
Intel Minnowboard Max instructions:
This uses as FSP as with Crown Bay, except it is for the Atom E3800 series.
@@ -136,6 +135,24 @@ Now you can build U-Boot and obtain u-boot.rom
$ make minnowmax_defconfig
$ make all
+Intel Galileo instructions:
+
+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
+needed by the Quark SoC itself.
+
+You can get the binary blob from Quark Board Support Package from Intel website:
+
+* ./QuarkSocPkg/QuarkNorthCluster/Binary/QuarkMicrocode/RMU.bin
+
+Rename the file and put it to the board directory by:
+
+ $ cp RMU.bin board/intel/galileo/rmu.bin
+
+Now you can build U-Boot and obtain u-boot.rom
+
+$ make galileo_defconfig
+$ make all
Test with coreboot
------------------
@@ -203,7 +220,6 @@ mtrr - List and set the Memory Type Range Registers (MTRR). These are used to
Development Flow
----------------
-
These notes are for those who want to port U-Boot to a new x86 platform.
Since x86 CPUs boot from SPI flash, a SPI flash emulator is a good investment.