summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2018-08-10 02:39:35 -0700
committerBin Meng <bmeng.cn@gmail.com>2018-08-20 13:52:49 +0800
commit1cf6825a681c289032f6309d3ac5eab2fd71a703 (patch)
tree28a16cd52920aca9b9d0306faf51c17393843d56 /doc
parent6e71a6ab2d9e06a275e40a8c5c8e0b29cf6bb8fb (diff)
downloadu-boot-1cf6825a681c289032f6309d3ac5eab2fd71a703.tar.gz
u-boot-1cf6825a681c289032f6309d3ac5eab2fd71a703.tar.bz2
u-boot-1cf6825a681c289032f6309d3ac5eab2fd71a703.zip
x86: dts: Remove coreboot_fb.dtsi
There is no need to keep a separate coreboot_fb.dtsi since now we have a generic coreboot payload dts. While we are here, this also remove the out-of-date description in the documentation regarding to coreboot framebuffer driver with U-Boot loaded as a payload from coreboot. As the testing result with QEMU 2.5.0 shows, the driver just works like a charm. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/README.x867
1 files changed, 0 insertions, 7 deletions
diff --git a/doc/README.x86 b/doc/README.x86
index 6015ca4011..8cc46725f2 100644
--- a/doc/README.x86
+++ b/doc/README.x86
@@ -412,17 +412,10 @@ To enable video you must enable these options in coreboot:
- Set framebuffer graphics resolution (1280x1024 32k-color (1:5:5))
- Keep VESA framebuffer
-And include coreboot_fb.dtsi in your board's device tree source file, like:
-
- /include/ "coreboot_fb.dtsi"
-
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