From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109763] [radeonsi] Enable framerate capping
Date: Mon, 18 Mar 2019 20:09:30 +0000 [thread overview]
Message-ID: <bug-109763-502-Kdgrj5Jyms@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109763-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1126 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109763
--- Comment #14 from Shmerl <shtetldik@gmail.com> ---
(In reply to Kristoffer from comment #13)
> I believe Chill might be encumbered by patents so I'm not sure an open
> source implementation is legally possible.
>
> https://patents.google.com/patent/US20080055318A1/
>
> It's also quite a bit more complicated than a static framerate limiter,
> requiring monitoring of on-screen movement and input events to constantly
> evaluate what framerate is appropriate in each moment.
>
> A static framerate limiter would be nice though, but we already have
> libstrangle for that which works well most of the time.
I'd day better to have it upstream than separate, besides it's not always
working, especially for Vulkan.
In regards to patents, that's something that always can happen - you can never
be sure. If you are worried about that specific one from AMD, AMD can be
contacted about it. After all it's in their interest not to cause troubles to
Linux graphics stack.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2043 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 prev parent reply other threads:[~2019-03-18 20:09 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
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 [this message]
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-Kdgrj5Jyms@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.