summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2016-10-09 04:14:18 -0700
committerBin Meng <bmeng.cn@gmail.com>2016-10-12 10:58:24 +0800
commit2d3c573ee6373f4521491f1a38e81245c3a6be57 (patch)
tree4e75dfa2d62db43829a0092128ec054696a6c776 /doc
parent3968398eb2d974b4840d7210d8503d7cbd8f4c48 (diff)
x86: coreboot: Convert to use DM coreboot video driver
This converts coreboot to use DM framebuffer driver. 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.x864
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/README.x86 b/doc/README.x86
index c34f45586b..679955983b 100644
--- a/doc/README.x86
+++ b/doc/README.x86
@@ -381,6 +381,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.