summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2016-10-09 04:14:10 -0700
committerBin Meng <bmeng.cn@gmail.com>2016-10-12 10:55:38 +0800
commit4dc5e54da31c810c988a0122fcd50b7d6f70354a (patch)
treee5d8a97045971ab4d919a0a61bc792fe4f107074
parent54cd240731f904b5632e384e6d5b21777e36d86a (diff)
downloadu-boot-imx-4dc5e54da31c810c988a0122fcd50b7d6f70354a.zip
u-boot-imx-4dc5e54da31c810c988a0122fcd50b7d6f70354a.tar.gz
u-boot-imx-4dc5e54da31c810c988a0122fcd50b7d6f70354a.tar.bz2
x86: doc: Document coreboot framebuffer driver issue on QEMU
For some unknown reason, coreboot framebuffer driver never works on QEMU since day 1. It seems the driver only works on real hardware. Document this issue. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
-rw-r--r--doc/README.x863
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/README.x86 b/doc/README.x86
index ba5bb99..437dc29 100644
--- a/doc/README.x86
+++ b/doc/README.x86
@@ -385,6 +385,9 @@ At present it seems that for Minnowboard Max, coreboot does not pass through
the video information correctly (it always says the resolution is 0x0). This
works correctly for link though.
+Note: coreboot framebuffer driver does not work on QEMU. The reason is unknown
+at this point. Patches are welcome if you figure out anything wrong.
+
Test with QEMU for bare mode
----------------------------
QEMU is a fancy emulator that can enable us to test U-Boot without access to