summaryrefslogtreecommitdiffstats
path: root/include/video_fb.h
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2014-11-14 20:56:33 -0700
committerSimon Glass <sjg@chromium.org>2014-11-25 07:11:14 -0700
commit6854f87cbcad544dc07a02b96d358f81ca60c593 (patch)
tree228c9d727db6d46449debc7bd10b59f0964277e5 /include/video_fb.h
parent0ca2426beae04189f094180748e72463f48a9270 (diff)
downloadblackbird-obmc-uboot-6854f87cbcad544dc07a02b96d358f81ca60c593.tar.gz
blackbird-obmc-uboot-6854f87cbcad544dc07a02b96d358f81ca60c593.zip
pci: Add general support for execution of video ROMs
Some platforms don't have native code for dealing with their video hardware. In some cases they use a binary blob to set it up and perform required actions like setting the video mode. This approach is a hangover from the old PC days where a ROM was provided and executed during startup. Even now, these ROMs are supplied as a way to set up video. It avoids the code for every video chip needing to be provided in the boot loader. But it makes the video much less flexible - e.g. it is not possible to do anything else while the video init is happening (including waiting hundreds of milliseconds for display panels to start up). In any case, to deal with this sad state of affairs, provide an API for execution of x86 video ROMs, either natively or through emulation. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'include/video_fb.h')
-rw-r--r--include/video_fb.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/video_fb.h b/include/video_fb.h
index 6cd4e377c2..55ec24dbee 100644
--- a/include/video_fb.h
+++ b/include/video_fb.h
@@ -40,7 +40,7 @@
/* Export Graphic Driver Control */
/******************************************************************************/
-typedef struct {
+typedef struct graphic_device {
unsigned int isaBase;
unsigned int pciBase;
unsigned int dprBase;
OpenPOWER on IntegriCloud