summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2015-06-03 09:20:04 +0800
committerSimon Glass <sjg@chromium.org>2015-06-04 03:03:18 -0600
commit683b09d7837a71fb4c5dd53919c6afa4d800e60e (patch)
tree76dbdf8573491875de5b7fef84cdcc296ec9f368 /doc
parent65cdd9be3e0fe79909962bba9bedf7967d44d60b (diff)
downloadblackbird-obmc-uboot-683b09d7837a71fb4c5dd53919c6afa4d800e60e.tar.gz
blackbird-obmc-uboot-683b09d7837a71fb4c5dd53919c6afa4d800e60e.zip
x86: qemu: Create separate i440fx and q35 device trees
Although the two qemu-x86 targets (i440fx and q35) share a lot in common, they still have something that cannot easily handled in one single device tree). Split to create two dedicated device tree files and make the i440fx be the default build target. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/README.x8610
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/README.x86 b/doc/README.x86
index 0726205540..c19f4a03ba 100644
--- a/doc/README.x86
+++ b/doc/README.x86
@@ -40,7 +40,7 @@ configuration during the 'make menuconfig' process.
x86 architecture --->
...
(qemu-x86) Board configuration file
- (qemu-x86) Board Device Tree Source (dts) file
+ (qemu-x86_i440fx) Board Device Tree Source (dts) file
(0x01920000) Board specific Cache-As-RAM (CAR) address
(0x4000) Board specific Cache-As-RAM (CAR) size
@@ -186,6 +186,14 @@ To build u-boot.rom for QEMU x86 targets, just simply run
$ make qemu-x86_defconfig
$ make all
+Note this default configuration will build a U-Boot for the QEMU x86 i440FX
+board. To build a U-Boot against QEMU x86 Q35 board, you can change the build
+configuration during the 'make menuconfig' process like below:
+
+Device Tree Control --->
+ ...
+ (qemu-x86_q35) Default Device Tree for DT control
+
Test with coreboot
------------------
For testing U-Boot as the coreboot payload, there are things that need be paid
OpenPOWER on IntegriCloud