From: Gerd Hoffmann <kraxel@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
"Michael S. Tsirkin" <mst@redhat.com>,
"Dr. David Alan Gilbert"
<dgilbert@redhat.com>qemu-ppc@nongnu.org,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [RfC PATCH] vga: wire up -g <width>x<height> switch for virtio and qxl
Date: Tue, 21 Feb 2017 15:42:20 +0100 [thread overview]
Message-ID: <1487688140.2694.84.camel@redhat.com> (raw)
In-Reply-To: <02a49a30-aa68-6484-0957-85009948296e@redhat.com>
Hi,
> I think the basic idea of the patch is good, but I'd remove the qxl
> FIXMEs for the final version of the patch (spice is likely not working
> on Sparc and PPC anyway yet).
Sure, just wanted have a rfc out of the door before going debug the qxl
issue.
> > -#ifdef TARGET_SPARC
> > +#if defined(TARGET_SPARC)
> > int graphic_width = 1024;
> > int graphic_height = 768;
> > int graphic_depth = 8;
> > -#else
> > +#elif defined(TARGET_PPC)
> > int graphic_width = 800;
> > int graphic_height = 600;
> > int graphic_depth = 32;
> > +#else
> > +int graphic_width;
> > +int graphic_height;
> > +int graphic_depth;
> > #endif
>
> IMHO we could also switch the default resolution on ppc to 1024x768, so
> you could simplify that code to something like that:
Cc'ing qemu-ppc list. Comments on the suggestion?
> And maybe Sparc can even work fine with 32 bpp nowadays, too, so you
> could completely get rid of the ifdefery here?
Depends on the sparc display devices, so no for the general case.
I think the better policy would be to just not initialize the graphics_*
variables and let the machine and/or display adapter pick a sane default
then.
cheers,
Gerd
next prev parent reply other threads:[~2017-02-21 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 15:16 [Qemu-devel] [RfC PATCH] vga: wire up -g <width>x<height> switch for virtio and qxl Gerd Hoffmann
2017-02-20 15:34 ` no-reply
2017-02-20 15:54 ` Thomas Huth
2017-02-21 14:42 ` Gerd Hoffmann [this message]
2017-02-20 17:51 ` Laszlo Ersek
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=1487688140.2694.84.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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.