qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <Laurent.Vivier@bull.net>
To: qemu-devel@nongnu.org
Cc: bochs developers <bochs-developers@lists.sourceforge.net>,
	kvm developers <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH 0/3] Add BIOS splash image support
Date: Wed, 17 Dec 2008 14:09:15 +0100	[thread overview]
Message-ID: <1229519355.4116.6.camel@frecb07144> (raw)
In-Reply-To: <4948435D.1090204@gmx.net>

Le mercredi 17 décembre 2008 à 01:10 +0100, Carl-Daniel Hailfinger a
écrit :
> On 16.12.2008 22:51, Laurent Vivier wrote:
> > Le mardi 16 décembre 2008 à 22:46 +0200, Blue Swirl a écrit :
> >   
> >> On 12/16/08, Anthony Liguori <anthony@codemonkey.ws> wrote:
> >>     
> >>> Blue Swirl wrote:
> >>>       
> >
> >   
> >>>>  The control channel may still be needed.
> >>>>
> >>>> Alternatively the BIOS could load the image and fade parameters from a
> >>>> new ROM or from the configuration device and draw it to screen. This
> >>>> would need some PNG support to BIOS, or that the image stored in raw
> >>>> form.
> >>>>
> >>>>
> >>>>         
> >>>  Yeah, having QEMU render to the VGA directly is a bit ugly.  It would be
> >>> nicer if the BIOS actually rendered the image but I'm not sure I think we
> >>> should reject the patch just because it doesn't.
> >>>       
> >> Actually this way the image can be in full color even if the emulated
> >> device was an EGA in text mode.
> >>     
> >
> > And you can provide the image name on the command line, and complexity
> > is in Qemu, not in BIOS.
> >   
> 
> 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.
> >   
> 
> 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
-- 
------------------ Laurent.Vivier@bull.net  ------------------
"Tout ce qui est impossible reste à accomplir"    Jules Verne
"Things are only impossible until they're not" Jean-Luc Picard

  reply	other threads:[~2008-12-17 13:09 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 15:20 [Qemu-devel] [PATCH 0/3] Add BIOS splash image support Laurent Vivier
2008-12-16 15:20 ` [Qemu-devel] [PATCH 1/3] Correct fw_cfg_add_callback() Laurent Vivier
2008-12-16 15:20   ` [Qemu-devel] [PATCH 2/3] [BIOS] Add splash image support Laurent Vivier
2008-12-16 15:20     ` [Qemu-devel] [PATCH 3/3] [QEMU] Add BIOS splash image Laurent Vivier
2008-12-16 15:33       ` Andreas Färber
2008-12-16 17:22         ` Laurent Vivier
2008-12-16 16:16       ` Blue Swirl
2008-12-16 17:32         ` Laurent Vivier
2008-12-16 17:41           ` Blue Swirl
2008-12-16 17:58             ` Laurent Vivier
2008-12-16 20:06 ` [Qemu-devel] [PATCH 0/3] Add BIOS splash image support Blue Swirl
2008-12-16 20:28   ` Anthony Liguori
2008-12-16 20:46     ` Blue Swirl
2008-12-16 21:51       ` Laurent Vivier
2008-12-17  0:10         ` Carl-Daniel Hailfinger
2008-12-17 13:09           ` Laurent Vivier [this message]
2008-12-17 16:21             ` [Bochs-developers] " Carl-Daniel Hailfinger
2008-12-17 22:58           ` [Bochs-developers] [Qemu-devel] [PATCH 0/3] Add BIOS splashimage support Sebastian Herbszt
2008-12-17 11:03     ` [Qemu-devel] [PATCH 0/3] Add BIOS splash image support Daniel P. Berrange
2008-12-17 13:18       ` Paul Brook
2008-12-17 13:45         ` Jan Kiszka
2008-12-17 13:55           ` Gleb Natapov
2008-12-17 14:53             ` Jan Kiszka
2008-12-17 15:06               ` Jan Kiszka
2008-12-17 15:17               ` Paul Brook
2008-12-17 16:35                 ` Jan Kiszka
2008-12-17 17:14                   ` Anthony Liguori
2008-12-17 18:30                     ` Jan Kiszka
2008-12-17 18:43                       ` Anthony Liguori
2008-12-17 18:09                   ` Andreas Färber
2008-12-17 17:15                 ` Anthony Liguori
2008-12-17 22:28                   ` Sebastian Herbszt
2008-12-18  8:59                     ` Volker Ruppert
2008-12-18 21:46                       ` H. Peter Anvin
2008-12-17 17:12             ` Carl-Daniel Hailfinger
2008-12-17 14:49           ` Gerd Hoffmann
2008-12-17 14:54             ` Jan Kiszka
2008-12-17 15:04               ` Kevin Wolf
2008-12-17 15:26                 ` Daniel P. Berrange
2008-12-17 16:44                   ` [Qemu-devel] " Jan Kiszka
2008-12-17 17:06                     ` Gildas
2008-12-17 17:22                       ` M. Warner Losh
2008-12-17 17:17                     ` Gleb Natapov
2008-12-17 18:01                       ` Anthony Liguori
2008-12-17 22:03                         ` [Qemu-devel] " Sebastian Herbszt
2008-12-17 22:09                           ` [Qemu-devel] " Anthony Liguori
2008-12-17 14:01         ` [Qemu-devel] " Daniel P. Berrange
2008-12-17 13:51   ` Kevin O'Connor
2008-12-17 21:58 ` [Qemu-devel] Re: [Bochs-developers] " Sebastian Herbszt
2008-12-17 23:24   ` Laurent Vivier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1229519355.4116.6.camel@frecb07144 \
    --to=laurent.vivier@bull.net \
    --cc=bochs-developers@lists.sourceforge.net \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).