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-ayl...@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
