All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Breuer <breuerr@mc.net>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] selecting a sparc framebuffer from command line
Date: Tue, 26 Mar 2013 10:08:58 -0500	[thread overview]
Message-ID: <5151BA0A.1040000@mc.net> (raw)
In-Reply-To: <CACXAS8AhqUv02THXEBDdqPaOEDKO9HWarovxxv0HuFG-pAbw7Q@mail.gmail.com>

On 3/26/2013 6:13 AM, Artyom Tarasenko wrote:
> It looks like we will have more framebuffers beside TCX in the near future.
> One way to use them would be to make new machines combining a base
> machine name with a framebuffer name, like ss5tcx and ss5cg3, but I
> guess this would produce too many machines if we have more than 2
> framebuffers.
> 
> Should the "-vga" option be (mis)used for selecting a framebuffer?
> They are not called "VGA" in the wild, but maybe the name VGA is
> obvious enough for a modern user? After all there is already a "-hda"
> option in the SPARCStation-5 emulation command line, although in the
> non-emulating world no one calls scsi disk "hda".
> 
> Or should an architecture-specific option, like -framebuffer be added?
> 

I would like to see -device used.  With a better sbus framework, adding
multiple video devices on sparc32 should be really easy to do.

I just looked at how "-device cirrus-vga" works.  To get -device to
override the default video, we need to add minimal support into vl.c to
recognize each video device and handle the default_vga flag.  Then
sparc32 could limit itself to handling either VGA_NONE or VGA_STD when
it adds the default video.

Bob

  reply	other threads:[~2013-03-26 15:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 11:13 [Qemu-devel] selecting a sparc framebuffer from command line Artyom Tarasenko
2013-03-26 15:08 ` Bob Breuer [this message]
2013-03-26 17:24   ` Artyom Tarasenko
2013-03-27 14:54     ` Bob Breuer
2013-03-27 16:43       ` Artyom Tarasenko
2013-03-28 11:46         ` [Qemu-devel] [OpenBIOS] " Mark Cave-Ayland
2013-03-30 13:18           ` Blue Swirl

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=5151BA0A.1040000@mc.net \
    --to=breuerr@mc.net \
    --cc=atar4qemu@gmail.com \
    --cc=blauwirbel@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.