From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LCw9i-0002vz-1N for qemu-devel@nongnu.org; Wed, 17 Dec 2008 08:09:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LCw9g-0002ve-UK for qemu-devel@nongnu.org; Wed, 17 Dec 2008 08:09:37 -0500 Received: from [199.232.76.173] (port=48980 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LCw9g-0002va-PB for qemu-devel@nongnu.org; Wed, 17 Dec 2008 08:09:36 -0500 Received: from ecfrec.frec.bull.fr ([129.183.4.8]:34324) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LCw9g-00066E-7w for qemu-devel@nongnu.org; Wed, 17 Dec 2008 08:09:36 -0500 Subject: Re: [Qemu-devel] [PATCH 0/3] Add BIOS splash image support From: Laurent Vivier In-Reply-To: <4948435D.1090204@gmx.net> References: <1229440810-12394-1-git-send-email-Laurent.Vivier@bull.net> <49480F6D.2010302@codemonkey.ws> <1229464268.26715.12.camel@frecb07144> <4948435D.1090204@gmx.net> Content-Type: text/plain; charset=utf-8 Date: Wed, 17 Dec 2008 14:09:15 +0100 Message-Id: <1229519355.4116.6.camel@frecb07144> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: bochs developers , kvm developers Le mercredi 17 d=C3=A9cembre 2008 =C3=A0 01:10 +0100, Carl-Daniel Hailfin= ger a =C3=A9crit : > On 16.12.2008 22:51, Laurent Vivier wrote: > > Le mardi 16 d=C3=A9cembre 2008 =C3=A0 22:46 +0200, Blue Swirl a =C3=A9= crit : > > =20 > >> On 12/16/08, Anthony Liguori wrote: > >> =20 > >>> Blue Swirl wrote: > >>> =20 > > > > =20 > >>>> The control channel may still be needed. > >>>> > >>>> Alternatively the BIOS could load the image and fade parameters fr= om a > >>>> new ROM or from the configuration device and draw it to screen. Th= is > >>>> would need some PNG support to BIOS, or that the image stored in r= aw > >>>> form. > >>>> > >>>> > >>>> =20 > >>> Yeah, having QEMU render to the VGA directly is a bit ugly. It wo= uld be > >>> nicer if the BIOS actually rendered the image but I'm not sure I th= ink we > >>> should reject the patch just because it doesn't. > >>> =20 > >> Actually this way the image can be in full color even if the emulate= d > >> device was an EGA in text mode. > >> =20 > > > > And you can provide the image name on the command line, and complexit= y > > is in Qemu, not in BIOS. > > =20 >=20 > If one of the goals of QEMU is to be somewhat similar to hardware, this > should be done in the BIOS. A lot of things in Qemu are already not similar to hardware: virtio, firmware configuration device, instruction timing... > What happens if the BIOS provides a splash screen? Will it override the > QEMU splash screen? Yes. The BIOS asks Qemu to display the image... or not. > > But in fact, my first idea was to read the image data from the > > configuration device (which is always possible with LOGO_CMD_OFFSET), > > but when I saw how it has been done in VirtualBox, I though it was a > > good idea. > > =20 >=20 > Modern x86 BIOSes read the splash screen from the BIOS ROM and the > settings from NVRAM (sometimes the BIOS ROM is used for that as well by > reflashing a sector of the ROM on every boot). A BIOS, by definition, is not modern... ;-) (Openfirmware is...) Laurent --=20 ------------------ Laurent.Vivier@bull.net ------------------ "Tout ce qui est impossible reste =C3=A0 accomplir" Jules Verne "Things are only impossible until they're not" Jean-Luc Picard