From: Gerd Hoffmann <kraxel@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Programmingkid <programmingkidx@gmail.com>,
"list@suse.de:PowerPC list:PowerPC" <qemu-ppc@nongnu.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Adding resolutions to the VGA driver
Date: Fri, 16 Sep 2016 12:58:52 +0200 [thread overview]
Message-ID: <1474023532.5756.19.camel@redhat.com> (raw)
In-Reply-To: <1473977179.8689.370.camel@kernel.crashing.org>
On Fr, 2016-09-16 at 08:06 +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2016-09-15 at 13:21 -0400, Programmingkid wrote:
> > There has been talk about what resolutions to add support for in the
> > VGA driver. What do you think of this list:
Which driver?
Linux kernel driver just uses the kernel's internal mode database,
beside that you can add anything you want (for example via xrandr).
> We should add check for the vram amount. There's only 16M emulated
> iirc, we need to check the combination resolution/depth fits.
Yes, vram size should be checked, at runtime. 16M is just the default,
you can have anything from 1M to 256M.
cheers,
Gerd
next prev parent reply other threads:[~2016-09-16 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 17:21 [Qemu-devel] Adding resolutions to the VGA driver Programmingkid
2016-09-15 22:06 ` Benjamin Herrenschmidt
2016-09-16 10:58 ` Gerd Hoffmann [this message]
2016-09-16 12:26 ` Benjamin Herrenschmidt
2016-09-17 2:53 ` [Qemu-devel] VGA driver debug output G 3
2016-09-17 3:30 ` Benjamin Herrenschmidt
2016-09-16 8:37 ` [Qemu-devel] Adding resolutions to the VGA driver Michael Fritscher
2016-09-16 8:56 ` Benjamin Herrenschmidt
2016-09-16 10:13 ` Michael Fritscher
2016-09-16 12:25 ` Benjamin Herrenschmidt
2016-09-16 11:32 ` G 3
2016-09-17 7:59 ` Michael Tokarev
2016-09-17 21:28 ` G 3
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=1474023532.5756.19.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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.