From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110137] drirc adaptive sync, vrr, freesync blacklisting documentation
Date: Sat, 16 Mar 2019 02:18:46 +0000 [thread overview]
Message-ID: <bug-110137-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1151 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110137
Bug ID: 110137
Summary: drirc adaptive sync, vrr, freesync blacklisting
documentation
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: grmat@sub.red
QA Contact: dri-devel@lists.freedesktop.org
Hi,
using qutebrowser in fullscreen mode breaks the video output with VRR enabled
because it refreshes very unsteadily, which is typical for a browser. Some
browsers are blacklisted in the drirc. I've added the following lines to the
drirc, but it doesn't disable VRR for a fullscreen qutebrowser window.:
<application name="qutebrowser" executable="qutebrowser">
<option name="adaptive_sync" value="false" />
</application>
Is there any documentation about how the matching works?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2574 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-03-16 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 2:18 bugzilla-daemon [this message]
2019-03-18 12:56 ` [Bug 110137] drirc adaptive sync, vrr, freesync blacklisting documentation bugzilla-daemon
2019-04-09 9:14 ` bugzilla-daemon
2019-04-09 13:08 ` bugzilla-daemon
2019-09-25 18:49 ` 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-110137-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.