Hi Martin,
I already planed to do it very soon if there is no other activity. Shouldn't be 
so hard to implement. Thank you for syncing with me.
Best regards -Carsten


Von meinem Samsung Galaxy Smartphone gesendet.
-------- Ursprüngliche Nachricht --------Von: Martin Peres 
<martin.pe...@free.fr> Datum: 04.10.18  09:42  (GMT+01:00) An: Michel Dänzer 
<mic...@daenzer.net>, Carsten Behling <carsten.behl...@googlemail.com> Cc: 
x...@freedesktop.org Betreff: Re: modesetting TearFree / VSYNC aware rotation 
pageflipping 
On 03/10/2018 17:36, Michel Dänzer wrote:
> On 2018-10-03 4:22 p.m., Carsten Behling wrote:
>>
>>> TearFree uses separate dedicated scanout buffers, to which the "main"
>>> buffer contents are copied on demand.
>>>
>>> Originally, these three things (DRI page flipping, rotation and
>>> TearFree) were separate and mutually exclusive. However, the
>>> amdgpu/radeon drivers support all of them the same time these days; this
>>> still requires an extra copy in some cases, but that could be eliminated
>>> at least in the non-rotated DRI page flipping case.
>>>
>>> https://gitlab.freedesktop.org/xorg/xserver/merge_requests/24 has the
>>> start of TearFree support for the modesetting driver, but it's still
>>> mutually exclusive with rotation (DRI3 page flipping should work with
>>> TearFree, but may still exhibit tearing if the client/user disables
>>> sync-to-vblank).
>>
>> Couldn't we extend modesetting in addition to Martin's TearFree patch the
>> same way you did here for Radeon?:
>>
>> https://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=798c4fd16d339b1ad5fd729cc884be084c60e38b
> 
> Yeah, something like that would be needed.
> 

Carsten,

Would you like to add support for it on top of my branch? I am a bit
swamped but I could be convinced to help you on this if needed :)

Martin
_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Reply via email to