From: G 3 <programmingkidx@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Questions about EDID
Date: Tue, 26 Feb 2019 16:11:06 -0500 [thread overview]
Message-ID: <CAKyx-3OOkkdSQ=UAucP_ZpormrEczwNhEpAnVtFeQOSOrnD7Vg@mail.gmail.com> (raw)
In-Reply-To: <20190226064347.i5kvwazmz3xcupkj@sirius.home.kraxel.org>
When I use edid=on, I do see a lot of extra resolutions available in Mac OS
9 and Mac OS X, just not the resolution I want to use. Is there some kind
of rule like the resolution value has to be divisible by a certain number?
On Tue, Feb 26, 2019 at 1:43 AM Gerd Hoffmann <kraxel@redhat.com> wrote:
> On Mon, Feb 25, 2019 at 09:49:22PM -0500, Programmingkid wrote:
> >
> > > On Feb 25, 2019, at 10:26 AM, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > >
> > > On Mon, Feb 25, 2019 at 09:05:30AM -0500, G 3 wrote:
> > >> Hi Gerd, I was wondering if you have made any documentation for your
> EDID
> > >> patches. If you have could you provide a link please?
> > >
> > > No docs.
> > >
> > >> Also could a feature be added that allows the user to specify
> resolutions
> > >> to be made available to the guest?
> > >>
> > >> Maybe it could work like this: -device
> VGA,edid=on,res=1366x768,7680x4320
> > >
> > > A single resolution works (via xres + yres properties).
> >
> > Could you send an example of the xres and yres properties please?
> > I tried this but it didn't work: -device VGA,edid=on,xres=999,yres=888
>
> That is correct. But you also need a guest driver with edid support.
>
> I think the macos driver got support for that, for linux support landed
> in the 5.0 devel cycle.
>
> cheers,
> Gerd
>
>
next prev parent reply other threads:[~2019-02-26 21:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 14:05 [Qemu-devel] Questions about EDID G 3
2019-02-25 15:26 ` Gerd Hoffmann
2019-02-26 2:49 ` Programmingkid
2019-02-26 6:43 ` Gerd Hoffmann
2019-02-26 21:11 ` G 3 [this message]
2019-02-27 5:27 ` Gerd Hoffmann
2019-02-27 21:22 ` Programmingkid
2019-02-28 5:01 ` Mark Cave-Ayland
2019-02-28 5:49 ` Gerd Hoffmann
2019-02-28 6:01 ` Mark Cave-Ayland
2019-02-28 6:38 ` Gerd Hoffmann
2019-02-28 16:57 ` Mark Cave-Ayland
2019-03-01 5:43 ` Gerd Hoffmann
2019-02-28 16:53 ` G 3
2019-03-01 5:47 ` Gerd Hoffmann
2019-03-01 14:41 ` 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='CAKyx-3OOkkdSQ=UAucP_ZpormrEczwNhEpAnVtFeQOSOrnD7Vg@mail.gmail.com' \
--to=programmingkidx@gmail.com \
--cc=kraxel@redhat.com \
--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.