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: Wed, 13 Mar 2019 13:07:25 +0000 [thread overview]
Message-ID: <bug-201795-2300-4wj2bNebNt@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 #16 from Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) ---
By default, amdgpu DC doesn't perform any sort of display scaling. It relies on
the monitor/TV's scaler itself to do the work, which might be producing the
black bars.
When you do set the scaling mode via the connector property "scaling mode", the
driver will perform the scaling itself. However, this scaling is done on
whatever the preferred mode for the monitor is.
I believe that the preferred mode for your TV is 4096x2160:
"4096x2160" 30 297000 4096 4184 4272 4400 2160 2168 2178 2250 0x40 0x5
This should be the timing used when display scaling is done by the driver
itself. You might get mirroring to work if you set the connector scaling mode
property, eg:
xrandr --output DisplayPort-0 --set "scaling mode" "Full"
and then try changing the mode on the display or mirroring.
This setting can persist in your xorg.conf as well, I believe it looks
something like:
Section "Monitor"
Identifier "DisplayPort-0"
Option "scaling mode" "Full"
EndSection
--
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-13 13:07 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 [this message]
2019-03-13 19:13 ` bugzilla-daemon
2019-03-13 20:02 ` bugzilla-daemon
2019-03-15 7:54 ` bugzilla-daemon
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-4wj2bNebNt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).