From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109763] [radeonsi] Enable framerate capping Date: Mon, 18 Mar 2019 20:09:30 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1532945284==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 6DEC08984D for ; Mon, 18 Mar 2019 20:09:30 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1532945284== Content-Type: multipart/alternative; boundary="15529397701.8df20bd4d.27122" Content-Transfer-Encoding: 7bit --15529397701.8df20bd4d.27122 Date: Mon, 18 Mar 2019 20:09:30 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D109763 --- Comment #14 from Shmerl --- (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. >=20 > https://patents.google.com/patent/US20080055318A1/ >=20 > 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. >=20 > 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 ne= ver 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. --=20 You are receiving this mail because: You are the assignee for the bug.= --15529397701.8df20bd4d.27122 Date: Mon, 18 Mar 2019 20:09:30 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 14 on bug 10976= 3 from = Shmerl 
(In reply to Kristoffer from comment #13)
> I believe Chill might be encumbered by patents s=
o I'm not sure an open
> source implementation is legally possible.
>=20
> https:/=
/patents.google.com/patent/US20080055318A1/
>=20
> It's also quite a bit more complicated than a static framerate limiter,
> requiring monitoring of on-screen movement and input events to constan=
tly
> evaluate what framerate is appropriate in each moment.
>=20
> 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 ne=
ver
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.
= --15529397701.8df20bd4d.27122-- --===============1532945284== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1532945284==--