From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52578 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OfyFZ-0004kd-77 for qemu-devel@nongnu.org; Mon, 02 Aug 2010 12:52:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OfyFX-00033g-Q1 for qemu-devel@nongnu.org; Mon, 02 Aug 2010 12:52:29 -0400 Received: from mail-qy0-f180.google.com ([209.85.216.180]:57834) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OfyFX-00033T-Nv for qemu-devel@nongnu.org; Mon, 02 Aug 2010 12:52:27 -0400 Received: by qyk31 with SMTP id 31so135945qyk.4 for ; Mon, 02 Aug 2010 09:52:26 -0700 (PDT) Message-ID: <4C56F7C6.8040204@codemonkey.ws> Date: Mon, 02 Aug 2010 11:52:22 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCHv3] Load "bootsplash.jpg" if present References: <20100802161157.GA11743@morn.localdomain> <4C56F35D.6020708@codemonkey.ws> <20100802164752.GA13438@morn.localdomain> In-Reply-To: <20100802164752.GA13438@morn.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin O'Connor Cc: qemu-devel@nongnu.org On 08/02/2010 11:47 AM, Kevin O'Connor wrote: > On Mon, Aug 02, 2010 at 11:33:33AM -0500, Anthony Liguori wrote: > >> On 08/02/2010 11:11 AM, Kevin O'Connor wrote: >> >>> Load the "bootsplash.jpg" file into fw_cfg if it is found in the roms >>> directory. >>> >> Sorry, I should have provided this in the first response. >> >> Does the bootsplash cause a delay in startup time? If so, we'll >> want to be able to disable this at boot time via the -boot option. >> If it doesn't, this patch is probably fine as is. >> > That's okay - the patch is intended to start discussion anyway. > > There is no added delay for the bootsplash. However, it does take > time to decompress it. On my machine it can take between 200-300ms > for the jpeg code. > > It may make more sense for SeaBIOS to only bother with the bootsplash > if the boot menu is enabled (or some new option) - as otherwise the > picture is basically cleared immiediately after it's shown. > Yeah, if there's no boot menu and no boot menu delay, I imagine the boot splash ends up just being a blip on the screen, right? We definitely want a "boot as fast as you possibly can" mode for the BIOS although for non-developer environments, I think a boot splash is a nice touch. BTW, we need to document somewhere any assumptions SeaBIOS has about the JPEG. I see that it expects a 1024x768 image. Any additional restrictions on the jpeg image? Regards, Anthony Liguori > -Kevin >