I have Weston without notify enabled, with this Weston my UI application
performance is fast.
But I changed to Weston with notify, because I have to start as system
service. I followed the procedure provided by you guys only.
Now my UI application performance has reduced means application gets
slo
Hi Scott,
As this was under discussion in last patchset, summarizing it here again:
HDCP2.2 spec leaves the content-type classification to the
content-provider (client).
The same had been discussed earlier in #wayland, and the mailing list:
https://lists.freedesktop.org/archives/wayland-deve
Clarify that after zwp_buffer_release_v1 events, otherwise unused
buffers can be reused without any additional implicit synchronization.
This is in contrast to wl_buffer.release, which doesn't guarantee that
implicit synchronization is not required to safely use a buffer after
the event is received
A series of assorted updates and clarifications for the
linux-explicit-synchronization protocol.
Alexandros Frantzis (3):
linux-explicit-synchronization: Allow fences with opaque EGL buffers
linux-explicit-synchronization: Warn about using the protocol while
using graphics APIs
linux-exp
Graphics APIs are expected to use this protocol under the hood, and
since there can only be one user of explicit synchronization per
surface, warn about using the protocol directly in such cases.
Signed-off-by: Alexandros Frantzis
---
.../linux-explicit-synchronization-unstable-v1.xml |
Add opaque EGL buffers to the supported buffer types for use with the
explicit synchronization protocol. Opaque EGL buffers rely on the same
EGL implementation in both the compositor and clients, which makes it
straightforward to manage client expectations about fence support for
such buffers.
Als
