From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:42181) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gzjLs-00067U-Ho for qemu-devel@nongnu.org; Fri, 01 Mar 2019 09:41:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gzjLr-0001X2-GO for qemu-devel@nongnu.org; Fri, 01 Mar 2019 09:41:28 -0500 Received: from mail-wr1-x42c.google.com ([2a00:1450:4864:20::42c]:33296) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gzjLr-0001W7-72 for qemu-devel@nongnu.org; Fri, 01 Mar 2019 09:41:27 -0500 Received: by mail-wr1-x42c.google.com with SMTP id i12so26187839wrw.0 for ; Fri, 01 Mar 2019 06:41:27 -0800 (PST) MIME-Version: 1.0 References: <20190225152618.r3epnypkpu6fyokt@sirius.home.kraxel.org> <20190226064347.i5kvwazmz3xcupkj@sirius.home.kraxel.org> <20190227052755.3lgo3265kaa6bzmi@sirius.home.kraxel.org> <1ef851d2-4148-56f0-65ac-a0e75022f20e@ilande.co.uk> <20190301054740.kmju3elrma5eqd4u@sirius.home.kraxel.org> In-Reply-To: <20190301054740.kmju3elrma5eqd4u@sirius.home.kraxel.org> From: G 3 Date: Fri, 1 Mar 2019 09:41:14 -0500 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Qemu-devel] Questions about EDID List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Mark Cave-Ayland , qemu-devel qemu-devel If the value is already in the list, then something else must be happening that prevents the custom resolution from reaching the guest. Would you know where in the list the custom resolution is added? My guess right now is the size of the list is being reported incorrectly - the custom resolution isn't being counted. When the operating system iterates thru the list it might stop right before the custom resolution value, preventing its inclusion. On Fri, Mar 1, 2019 at 12:47 AM Gerd Hoffmann wrote: > 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 > >