dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106040] [DC] HDMI Monitor has Overscan/Scaling
Date: Sat, 14 Apr 2018 01:10:52 +0000	[thread overview]
Message-ID: <bug-106040-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1577 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106040

            Bug ID: 106040
           Summary: [DC] HDMI Monitor has Overscan/Scaling
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: djbm@gnunorth.ca

Created attachment 138831
  --> https://bugs.freedesktop.org/attachment.cgi?id=138831&action=edit
Overscan issue on HP w2207h

With my HP w2207h monitor connected over HDMI, the image appears overscanned,
it is cut off at the sides and is upscaled (see attached image, note how the
top bar is missing with dc=1). It is possible to fit the image inside the
monitor with xset --set underscan on and xset --set "underscan
{hborder,vborder}", but this results in a blurry display.

This occurs with a RX Vega 64 and an RX 560 with amd-staging-drm-next commit
6d15a288b18119428b3af5d7a7641745e9f82860 (the latest at the time of testing) as
well as mainline 4.16.0. With the RX 560, the overscanning only occurs when the
new DC code is used, using the old code (with amdgpu.dc=0) results in a perfect
display. This also doesn't affect any other monitor I own using HDMI. 

Attached further are logs made with amdgpu.dc_log=1 and drm.debug=0x6 on the
Vega 64, the 560 with amdgpu.dc=1, and the 560 with amdgpu.dc=0.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3019 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

             reply	other threads:[~2018-04-14  1:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14  1:10 bugzilla-daemon [this message]
2018-04-14  1:11 ` [Bug 106040] [DC] HDMI Monitor has Overscan/Scaling bugzilla-daemon
2018-04-14  1:11 ` bugzilla-daemon
2018-04-14  1:11 ` bugzilla-daemon
2019-11-19  8:35 ` 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-106040-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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