Hello,
Using the VBT route for graphics initialisation and TianoCore as the payload gives two options within .config for splash screen:
CONFIG_BOOTSPLASH: This option shows a graphical bootsplash screen. The graphics are loaded from the CBFS file bootsplash.jpg.
CONFIG_TIANOCORE_BOOTSPLASH_IMAGE: Select this option if you have a bootsplash image that you would like to be used. If this option is not selected, the default coreboot logo (European Brown Hare) will used.
Do I need to define both? What are the requirements for the images in terms of size, colour depth, etc?
-Andy.
for Tianocore, use the latter only. Needs to be a 24bpp windows BMP, no larger than the width of the screen and 75% of the height (the image is centered 38.2% down from top as per BGRT spec). Gimp can be used too but likely will have a pallette shift if a non B&W image used
On Thu, Nov 26, 2020, 11:27 AM Andy Pont andy.pont@sdcsystems.com wrote:
Hello,
Using the VBT route for graphics initialisation and TianoCore as the payload gives two options within .config for splash screen:
CONFIG_BOOTSPLASH: This option shows a graphical bootsplash screen. The graphics are loaded from the CBFS file bootsplash.jpg.
CONFIG_TIANOCORE_BOOTSPLASH_IMAGE: Select this option if you have a bootsplash image that you would like to be used. If this option is not selected, the default coreboot logo (European Brown Hare) will used.
Do I need to define both? What are the requirements for the images in terms of size, colour depth, etc?
-Andy.
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Matt wrote…
for Tianocore, use the latter only. Needs to be a 24bpp windows BMP, no larger than the width of the screen and 75% of the height (the image is centered 38.2% down from top as per BGRT spec). Gimp can be used too but likely will have a pallette shift if a non B&W image used
Customer sent me a png image of the logo they want to use so have manipulated it using ImageMagick to give it a black background and convert it to a Windows 3.x format BMP at 24bpp. Not sure why but the first go converting it to a Windows 98/2000 and newer format failed.
Is there any reason not to use both with TianoCore? Does the CONFIG_BOOTSPLASH JPG file not spend long enough on screen to make it worthwhile using? I tried putting a JPG image (400x400 pixels) into Coreboot but jpeg_decode() didn’t like it and returned ERR_HEIGHT_MISMATCH. I haven’t looked into the cause (and may not do if it really isn’t needed).
-Andy.
On Thu, Nov 26, 2020 at 12:19 PM Andy Pont andy.pont@sdcsystems.com wrote:
Matt wrote…
for Tianocore, use the latter only. Needs to be a 24bpp windows BMP, no larger than the width of the screen and 75% of the height (the image is centered 38.2% down from top as per BGRT spec). Gimp can be used too but likely will have a pallette shift if a non B&W image used
Customer sent me a png image of the logo they want to use so have manipulated it using ImageMagick to give it a black background and convert it to a Windows 3.x format BMP at 24bpp. Not sure why but the first go converting it to a Windows 98/2000 and newer format failed.
Is there any reason not to use both with TianoCore? Does the CONFIG_BOOTSPLASH JPG file not spend long enough on screen to make it worthwhile using?
exactly this. On most devices, the payload will execute ~600ms after coreboot starts, and the image probably wouldn't start being displayed until halfway thru that. So it would be up for ~300ms and likely just appear as a flicker. Not to mention needing a different sized/formatted image than used for Tianocore
I tried putting a JPG image (400x400 pixels) into Coreboot but jpeg_decode() didn’t like it and returned ERR_HEIGHT_MISMATCH. I haven’t looked into the cause (and may not do if it really isn’t needed).
-Andy.
Matt wrote…
exactly this. On most devices, the payload will execute ~600ms after coreboot starts, and the image probably wouldn't start being displayed until halfway thru that. So it would be up for ~300ms and likely just appear as a flicker. Not to mention needing a different sized/formatted image than used for Tianocore
On that basis, should this either be added to the help on the BOOTSPLASH_IMAGE option or should the option be hidden if TIANOCORE_BOOTSPLASH_IMAGE is selected?
-Andy.
Andy Pont wrote:
I tried putting a JPG image (400x400 pixels) into Coreboot but jpeg_decode() didn’t like it and returned ERR_HEIGHT_MISMATCH.
I think the JPEG image height must match the (native) graphics mode.
I wasn't involved in that decision but I consider it a good thing, it ensures that a graphic is either presented correctly or not at all, with the latter case being detectable at runtime.
Thinking a little further, maybe coreboot could even allow including different versions of the image. (.ICO here we come..)
//Peter
-
Andy Pont -
Matt DeVillier -
Peter Stuge