From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH 0/3] Add BIOS splash image support Date: Wed, 17 Dec 2008 13:18:57 +0000 Message-ID: <200812171318.58650.paul@codesourcery.com> References: <1229440810-12394-1-git-send-email-Laurent.Vivier@bull.net> <49480F6D.2010302@codemonkey.ws> <20081217110319.GD13455@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Blue Swirl , bochs developers , kvm developers To: qemu-devel@nongnu.org, "Daniel P. Berrange" Return-path: Received: from mail.codesourcery.com ([65.74.133.4]:34635 "EHLO mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751009AbYLQNTB (ORCPT ); Wed, 17 Dec 2008 08:19:01 -0500 In-Reply-To: <20081217110319.GD13455@redhat.com> Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: > > Modern BIOSes have splash screens. I don't see why our BIOS shouldn't > > have one too. > > Crap PC BIOSes have splash screens because they're horribly slow > and otherwise printing lots of irrelevant scary junk at users. The > best BIOS 'splash' screen is one which never appears unless there > is a boot failure, and gets control to the OS as quickly as possible. > IMHO a better goal is reducing the time until the OS / bootloader is > able to take over all management of the display. I agree. The qemu bios init process takes almost no time. The only reason it takes a noticeable amount of time is that we have a deliberate delay in there to allow the user to access the boot menu. I'm not convinced this menu is actually very useful in practice, It's something that should probably be delegated to your management utility and/or be optional. Paul