summaryrefslogtreecommitdiff
path: root/src/include
diff options
context:
space:
mode:
authorJohanna Schander <coreboot@mimoja.de>2019-07-28 09:28:33 +0200
committerNico Huber <nico.h@gmx.de>2019-09-15 11:10:58 +0000
commitc544a85d2a211b04d224d2e21ea03aeedfa34dab (patch)
treecf24d783f19470f0ea3cc4b56fece8a05c557cdc /src/include
parentbfb0c2d543576f266e282a01f5bf1c074a890917 (diff)
downloadcoreboot-c544a85d2a211b04d224d2e21ea03aeedfa34dab.tar.xz
lib/coreboot_table: Show splashscreen in lb_table_init
Every vga init implementation needs to cache the framebuffer state to be able to fill the lb_framebuffer struct later on in the fill_lb_framebuffer call. Showing the bootsplash afterwards guarantees to have the same interface into all the vga drivers. This is by far from ideal, as it only allows for a single driver at compile-time and should be adapted in the future. It was tested on the wip razer blade stealth using vgabios @ 1280x1024 and also in Qemu @ 1280x1024. By default the qemu framebuffer will be initialized in 800x600@32. This can be overwriten by configuration by setting CONFIG_DRIVERS_EMULATION_QEMU_BOCHS_{X,Y}RES . Change-Id: I4bec06d22423627e8f429c4b47e0dc9920f1464e Signed-off-by: Johanna Schander <coreboot@mimoja.de> Reviewed-on: https://review.coreboot.org/c/coreboot/+/34599 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Nico Huber <nico.h@gmx.de>
Diffstat (limited to 'src/include')
-rw-r--r--src/include/bootsplash.h6
1 files changed, 0 insertions, 6 deletions
diff --git a/src/include/bootsplash.h b/src/include/bootsplash.h
index 84ba34cc90..af09922a5f 100644
--- a/src/include/bootsplash.h
+++ b/src/include/bootsplash.h
@@ -19,12 +19,6 @@
#include <types.h>
/**
- * Wraps bootsplash setup for vesa
- */
-void set_vesa_bootsplash(void);
-
-
-/**
* Sets up the framebuffer with the bootsplash.jpg from cbfs.
* Returns 0 on success
* CB_ERR on cbfs errors