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 109763] [radeonsi] Enable framerate capping
Date: Sun, 03 Mar 2019 21:41:24 +0000	[thread overview]
Message-ID: <bug-109763-502-Et2syQicly@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109763-502@http.bugs.freedesktop.org/>


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

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

--- Comment #8 from smoki <smoki00790@gmail.com> ---

 Just say, i wanna something like AMD FRTC for non FreeSync users and something
like AMD Chill for FreeSync users :D

 Both these could caps framerate just in a different enviroments and this is
where this become complicated as it depends what kind of screen you have these
days. If you are VRR capable you wanna something like Chill, otherwise FRTC :D

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

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

  parent reply	other threads:[~2019-03-03 21:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24 22:49 [Bug 109763] [radeonsi] Enable framerate capping bugzilla-daemon
2019-03-03 10:20 ` bugzilla-daemon
2019-03-03 10:22 ` bugzilla-daemon
2019-03-03 10:22 ` bugzilla-daemon
2019-03-03 10:28 ` bugzilla-daemon
2019-03-03 10:37 ` bugzilla-daemon
2019-03-03 20:40 ` bugzilla-daemon
2019-03-03 20:54 ` bugzilla-daemon
2019-03-03 21:41 ` bugzilla-daemon [this message]
2019-03-03 21:59 ` bugzilla-daemon
2019-03-03 22:03 ` bugzilla-daemon
2019-03-04  2:00 ` bugzilla-daemon
2019-03-04  2:03 ` bugzilla-daemon
2019-03-18 19:49 ` bugzilla-daemon
2019-03-18 20:09 ` bugzilla-daemon
2019-09-25 18:48 ` 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-109763-502-Et2syQicly@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