From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201795] [Regression] Wrong 4k resolution detected with DisplayPort to HDMI adapter on amdgpu
Date: Fri, 15 Mar 2019 07:54:54 +0000 [thread overview]
Message-ID: <bug-201795-2300-AvT5xD5bzY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201795-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201795
--- Comment #19 from thomas.lassdiesonnerein@gmx.de ---
Are you telling me, that the new code is better for most other users, and at
the same time works worse in my case, so you won't fix it? Then I appreciate
that you want me to understand this first and I will try now. Is the following
understanding correct?
Kernel <= 4.14: Scaling is ON by default. If users want a custom refresh rate
they would need switch scaling mode OFF via xorg.conf, but then get black bars.
Kernel > 4.14: If users want full screen instead of black bars, users have to
switch scaling mode ON via xorg.conf
Assessment:
Both are not intuitive. They relay on configuration file instead of a GUI
option in plain sight. Also: The black bars are more disturbing to the average
guy, than not to be able to set a custom refresh rate.
Idea:
Why does the driver not Scale ON by default AND sets the refresh rate of the
preferred mode?
I know I could be completely wrong here.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-15 7:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 19:30 [Bug 201795] New: [Regression] Wrong 4k resolution detected with DisplayPort to HDMI adapter on amdgpu bugzilla-daemon
2018-11-27 19:35 ` [Bug 201795] " bugzilla-daemon
2018-11-27 19:38 ` bugzilla-daemon
2018-11-27 19:39 ` bugzilla-daemon
2018-11-28 9:24 ` bugzilla-daemon
2018-11-28 19:23 ` bugzilla-daemon
2018-11-28 19:23 ` bugzilla-daemon
2018-11-28 19:24 ` bugzilla-daemon
2018-11-28 19:24 ` bugzilla-daemon
2018-11-29 8:39 ` bugzilla-daemon
2018-11-29 10:04 ` bugzilla-daemon
2018-12-15 7:12 ` bugzilla-daemon
2018-12-15 7:12 ` bugzilla-daemon
2018-12-15 16:53 ` bugzilla-daemon
2019-01-18 19:00 ` bugzilla-daemon
2019-01-23 11:19 ` bugzilla-daemon
2019-02-21 8:40 ` bugzilla-daemon
2019-03-13 11:00 ` bugzilla-daemon
2019-03-13 13:07 ` bugzilla-daemon
2019-03-13 19:13 ` bugzilla-daemon
2019-03-13 20:02 ` bugzilla-daemon
2019-03-15 7:54 ` bugzilla-daemon [this message]
2019-03-15 13:07 ` bugzilla-daemon
2019-03-15 13:43 ` bugzilla-daemon
2019-03-18 13:45 ` bugzilla-daemon
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=bug-201795-2300-AvT5xD5bzY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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.