From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103486] Tonga DC vblank_mode=0 not working as expected fullscreen
Date: Fri, 27 Oct 2017 15:50:41 +0000 [thread overview]
Message-ID: <bug-103486-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1111 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103486
Bug ID: 103486
Summary: Tonga DC vblank_mode=0 not working as expected
fullscreen
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: adf.lists@gmail.com
R9285, I notice that on both drm-next-4.15-dc and amd-staging-drm-next, when
using DC, vblank_mode=0 works windowed but not properly full screen.
Tried forcing TearFree from auto to off no difference.
There is no tearing where it would be expected - but it's not like it's just
being ignored, a bench mark test will cap fps at 2X refresh rate rather than
1X.
Maybe this is expected?
It doesn't happen with a months older DC kernel I have and looking at DC
benches on Phoronix I don't see any fps cap.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2395 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:[~2017-10-27 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 15:50 bugzilla-daemon [this message]
2017-10-27 16:14 ` [Bug 103486] Tonga DC vblank_mode=0 not working as expected fullscreen bugzilla-daemon
2017-10-27 20:17 ` bugzilla-daemon
2017-10-27 23:03 ` bugzilla-daemon
2017-10-31 20:57 ` bugzilla-daemon
2017-11-01 0:32 ` bugzilla-daemon
2017-11-01 0:39 ` bugzilla-daemon
2017-11-01 8:59 ` bugzilla-daemon
2017-11-01 17:07 ` bugzilla-daemon
2017-11-01 17:15 ` bugzilla-daemon
2017-11-01 17:20 ` bugzilla-daemon
2017-11-01 19:53 ` bugzilla-daemon
2017-11-15 21:44 ` 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-103486-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.