From: Thomas Zimmermann <tzimmermann@suse.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@cs.helsinki.fi>,
dri-devel@lists.freedesktop.org
Subject: Re: drm/ast something ate high-res modes (5.3->5.6 regression)
Date: Wed, 8 Jul 2020 13:41:25 +0200 [thread overview]
Message-ID: <f2b36a2e-baf7-ea23-fdb5-bfb7c54c0f4f@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.20.2007081246050.12041@whs-18.cs.helsinki.fi>
[-- Attachment #1.1.1: Type: text/plain, Size: 2827 bytes --]
Hi
Am 08.07.20 um 12:05 schrieb Ilpo Järvinen:
> Hi,
>
> After upgrading kernel from 5.3 series to 5.6.16 something seems to
> prevent me from achieving high resolutions with the ast driver.
Thanks for reporting. It's not a bug, but a side effect of atomic
modesetting.
During pageflips, the old code used to kick out the currently displayed
framebuffer and then load in the new one. If that failed, the display
went garbage.
In v5.6-rc1, we merged atomic modesetting for ast. This means that
screen updates are more reliable, but we have to over-commit resources.
Specifically, we have to reserve space for two buffers in video memory
while a pageflip happens. 1920x1200@32 are ~9MiB of framebuffer memory.
If your device has 16 MiB of VRAM, there's no space left for the second
framebuffer. Hence, the resolution is no longer supported.
On the positive side, you can now use Wayland compositors with ast.
Atomic modesetting adds the necessary interfaces.
Best regards
Thomas
>
> With 5.6.16:
>
> $ xrandr
> Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 1920 x 2048
> VGA-1 connected primary 1600x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
> 1600x1200 60.00*
> 1680x1050 59.95
> 1280x1024 75.02 60.02
> 1440x900 59.89
> 1280x800 59.81
> 1024x768 75.03 60.00
> 800x600 75.00 60.32
> 640x480 75.00 59.94
> 1920x1200_60.0 59.95
>
> If I try to change to that manually added high-res mode, I get:
> xrandr: Configure crtc 0 failed
>
> With 5.3 series I've this:
>
> Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 1920 x 2048
> VGA-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
> 1920x1200 59.95*+
> 1600x1200 60.00
> 1680x1050 59.95
> 1280x1024 75.02 60.02
> 1440x900 59.89
> 1280x800 59.81
> 1024x768 75.03 60.00
> 800x600 75.00 60.32
> 640x480 75.00 59.94
> 1920x1200_60.0 59.95
>
> As I've had issues in getting EDID reliably from the monitor, I provide it
> on kernel command-line (the one dumped from the monitor I use). In
> addition, I've another workaround for past issues related to EDID which
> always adds that 1920x1200_60.0 mode but now I cannot use even it to
> enter a high-res mode.
>
> If you need some additional info or want me to test a patch, just let me
> know (but some delay is expected in testing patches). Thanks.
>
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 516 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-07-08 11:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 10:05 drm/ast something ate high-res modes (5.3->5.6 regression) Ilpo Järvinen
2020-07-08 11:41 ` Thomas Zimmermann [this message]
2020-07-08 13:46 ` Ilpo Järvinen
2020-07-08 14:22 ` Thomas Zimmermann
2020-07-08 14:25 ` Thomas Zimmermann
2020-07-08 14:26 ` Daniel Vetter
2020-07-08 14:51 ` Thomas Zimmermann
2020-07-08 21:25 ` Ilpo Järvinen
2020-09-17 11:01 ` Thomas Zimmermann
2020-09-17 11:17 ` Ilpo Järvinen
2020-09-17 12:31 ` Thomas Zimmermann
2020-10-14 6:58 ` Ilpo Järvinen
2020-10-14 7:09 ` Thomas Zimmermann
2020-10-15 8:10 ` Ilpo Järvinen
2020-10-15 8:29 ` Thomas Zimmermann
2020-10-15 8:49 ` Ilpo Järvinen
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=f2b36a2e-baf7-ea23-fdb5-bfb7c54c0f4f@suse.de \
--to=tzimmermann@suse.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=ilpo.jarvinen@cs.helsinki.fi \
/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.