On Thu, 24 Jan 2019 11:47:30 +0200
Pekka Paalanen wrote:
> On Wed, 23 Jan 2019 18:43:52 +
> "Singh, Satyeshwar" wrote:
>
> > Imagine a benchmark case where the client renders for example 800
> > frames and attaches their buffer ids to a surface, the compositor
> > uses the last one that cam
On Wed, 23 Jan 2019 18:43:52 +
"Singh, Satyeshwar" wrote:
> Hey guys,
> As you know, Weston doesn't wait for client buffers to finish
> rendering. That is typically left as an exercise for the kernel mode
> graphics driver. I am wondering if anyone knows why this policy
> decision was made? M
On Wed, 23 Jan 2019 19:28:11 +
"Ucan, Emre (ADITG/ESB)" wrote:
> Hello Satyeshwar,
>
> nice to hear from you again (:
>
> short answer to your question: there is already implementation which is doing
> what you are asking:
> https://gitlab.freedesktop.org/wayland/weston/merge_requests/32
6937
From: wayland-devel On Behalf Of
Singh, Satyeshwar
Sent: Mittwoch, 23. Januar 2019 19:44
To: wayland-devel@lists.freedesktop.org
Subject: Should Weston wait for client buffers to finish rendering?
Hey guys,
As you know, Weston doesn't wait for client buffers to finish rendering. Tha
Hey guys,
As you know, Weston doesn't wait for client buffers to finish rendering. That
is typically left as an exercise for the kernel mode graphics driver. I am
wondering if anyone knows why this policy decision was made? More importantly,
is there any harm (or any side effect) that I am not t
