From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108941] Enabling PP_OVERDRIVE_MASK with dual monitors causes artifacting
Date: Tue, 04 Dec 2018 13:21:27 +0000 [thread overview]
Message-ID: <bug-108941-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1103 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108941
Bug ID: 108941
Summary: Enabling PP_OVERDRIVE_MASK with dual monitors causes
artifacting
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: boukehaarsma23@gmail.com
Steps to reproduce:
1) Have dual monitors
2) Enable PP_OVERDRIVE_MASK by flipping the appropriate bit in
amdgpu.ppfeaturemask. (For my configuration I used: 0xfffd7fff)
3) See artifacting.
When using default featuremask, or when using a single monitor with the
overdrive bit enabled behaves correctly. I heard multiple people who have the
same issue, so it does not seem related to my setup.
Setup:
RX480
Linux 4.20-rc5
If additional information is needed please let me know.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2394 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 reply other threads:[~2018-12-04 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 13:21 bugzilla-daemon [this message]
2018-12-04 13:44 ` [Bug 108941] Enabling PP_OVERDRIVE_MASK with dual monitors causes artifacting bugzilla-daemon
2018-12-04 14:10 ` bugzilla-daemon
2019-10-25 11:59 ` bugzilla-daemon
2019-11-19 9:06 ` 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-108941-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 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.