All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: G 3 <programmingkidx@gmail.com>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Questions about EDID
Date: Fri, 1 Mar 2019 06:47:40 +0100	[thread overview]
Message-ID: <20190301054740.kmju3elrma5eqd4u@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAKyx-3OsujsekrxTa1e=4FNb=pNQxELr8XccS9r2-9_9SxoWtQ@mail.gmail.com>

On Thu, Feb 28, 2019 at 11:53:43AM -0500, G 3 wrote:
> On Thu, Feb 28, 2019 at 12:01 AM Mark Cave-Ayland <
> mark.cave-ayland@ilande.co.uk> wrote:
> 
> > On 27/02/2019 05:27, Gerd Hoffmann wrote:
> >
> > > On Tue, Feb 26, 2019 at 04:11:06PM -0500, G 3 wrote:
> > >> 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?
> > >
> > > qemu doesn't have such a requirement.
> > > Might be the guest drivers have.
> > > Try making width/height multiple of 8 or 16.
> >
> > Right, at the moment all the MacOS driver does is parse the resolution
> > list from the
> > EDID and add them to the dropdown list - it doesn't support the xres and
> > yres properties.
> >
> 
> Gerd, could the xres +yres numbers be added to the list of resolutions
> then?

That is already the case:

qemu-edid -x 1234 -y 567 | edid-decode
[ ... ]
First detailed timing is preferred timing
Established timings supported:
  640x480@60Hz
  800x600@60Hz
  1024x768@60Hz
Standard timings supported:
  2048x1152@60Hz
  1920x1080@60Hz
Detailed mode: Clock 73.170 MHz, 485 mm x 223 mm
               1234 1542 1579 1665 hborder 0
               ^^^^
                567  569  571  586 vborder 0
                ^^^
               -hsync -vsync 
[ ... ]

cheers,
  Gerd

  reply	other threads:[~2019-03-01  5:47 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
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 [this message]
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=20190301054740.kmju3elrma5eqd4u@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=programmingkidx@gmail.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.