From 6544cb3f1b431f96bb6d16f86e2cb4f75a4188b3 Mon Sep 17 00:00:00 2001 From: Konstantin Aladyshev Date: Sat, 24 Jan 2015 18:52:10 +0400 Subject: Separate bootsplash image menuconfig option from others The possibility of adding a bootsplash image to ROM should be independent from VGA_ROM_RUN and VESA menuconfig options. For example, the stored image could be saved in CBFS not for coreboot but for later use in SeaBIOS. Change-Id: I3a0ed53489c40d4d44bd4ebc358ae6667e6c797f Signed-off-by: Konstantin Aladyshev Reviewed-on: http://review.coreboot.org/12129 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi --- src/device/Kconfig | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) (limited to 'src/device/Kconfig') diff --git a/src/device/Kconfig b/src/device/Kconfig index bcf7dad2a0..784b6d794c 100644 --- a/src/device/Kconfig +++ b/src/device/Kconfig @@ -556,15 +556,8 @@ config BOOTSPLASH This option shows a graphical bootsplash screen. The graphics are loaded from the CBFS file bootsplash.jpg. - You will be able to specify the location and file name of the - image later. - -config BOOTSPLASH_FILE - string "Bootsplash path and filename" - depends on BOOTSPLASH - default "bootsplash.jpg" - help - The path and filename of the file to use as graphical bootsplash - screen. The file format has to be jpg. + You can either specify the location and file name of the + image in the 'General' section or add it manually to CBFS, using, + for example, cbfstool. endmenu -- cgit v1.2.3