- Oct 11, 2016
-
-
Simon Glass authored
Provide a function to run the Vesa BIOS for a given PCI device and obtain the resulting configuration (e.g. display size) for use by the video uclass. This makes it easier to write a video driver that uses vesa and supports driver model. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com>
-
- Aug 26, 2015
-
-
Bin Meng authored
When booting as a coreboot payload, the framebuffer details are passed from coreboot via configuration tables. We save these information into vesa_mode_info structure for future use. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
-
- Jul 15, 2015
-
-
Bin Meng authored
Store VESA parameters to Linux setup header so that vesafb driver in the kernel could work. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org> Tested-by:
Jian Luo <jian.luo4@boschrexroth.de>
-
- Jan 24, 2015
-
-
Simon Glass authored
Allow the supported modes to be listed when in debug mode. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Nov 25, 2014
-
-
Simon Glass authored
For option ROMs we can use these extensions to request a particular video mode. Add a header file which defines the binary interface. Signed-off-by:
Simon Glass <sjg@chromium.org>
-