All of lore.kernel.org
 help / color / mirror / Atom feed
From: Programmingkid <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: Wed, 27 Feb 2019 16:22:13 -0500	[thread overview]
Message-ID: <601C46CD-AA96-4E51-A3E9-003153BA30AD@gmail.com> (raw)
In-Reply-To: <20190227052755.3lgo3265kaa6bzmi@sirius.home.kraxel.org>


> On Feb 27, 2019, at 12:27 AM, Gerd Hoffmann <kraxel@redhat.com> 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.


I counted 10 more added resolutions when using your edid feature on Mac OS 9.2 and on Mac OS 10.4. But when I tried adding one using the xres/yres properties, it didn't work. What operating system do you see success on? What is your command line you use?

I did try your suggestion by using 800x800 (16*50) resolution. It didn't work.'

Thank you.

  reply	other threads:[~2019-02-27 21:22 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 [this message]
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=601C46CD-AA96-4E51-A3E9-003153BA30AD@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.