Converted to JPG the file would be only about 9 kb.
It could be generated from this SVG file I attached. This could be generated in a scripted manner using free open source software tools such as the 'convert' utility, part of ImageMagick.
$ convert seabios.svg bootsplash.jpg
Convert also supports -size parameter to resize to different sizes.
The benefit of having it in the source tree is that it would make it easier for user to locate the path/directory where seabios looks for the bootsplash image, so they know where they should put their own bootsplash image. So they can just find the included bootsplash image and replace it with their own.
Having a prominent logo displayed may also result in SeaBIOS receiving more attention.
On Sun, Jan 29, 2012 at 6:32 AM, Peter Stuge firstname.lastname@example.org wrote:
Fred . wrote:
Add to source tree. bootsplash.bmp
I'm afraid that's not likely.
The file is 1.2 MB, which would grow the current repository size over 30%. I find that unacceptable for a bootsplash file that most will really notice or want.
Recall the discussion when you first brought up the bootsplash topic. SeaBIOS as you may have experienced by now only runs for a few hundred milliseconds, and in fact running the VGA BIOS takes most of that time, so a bootsplash would only be visible for maybe a tenth of a second. Suggesting to add artificial delays would not be wise.
Furthermore, if there is to be a bootsplash (which I for one don't hold for impossible) then it needs to be generated from the professional project logo (so far there is none) and preferably using scripted free and libre tools.
In any case, I think all graphics should be stored outside the source tree, and be an optional addon.
See e.g. what we do for the coreboot logo: http://coreboot.org/Logo
SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios