On 12 April 2011 21:04, Iskren Chernev wrote:
> I don't think this lengthy discussion led to any concrete answers, but I do
> think that the questions are important and need such answers.
> I'll try to summarize the problems that need attention:
> 1. screen locking
> 1.1 who is going to implement
2011/4/12 Marcus Lorentzon :
> Hi,
> we run Wayland on a platform without a MESA based EGL. But we still want to
> run the DRM compositor and use the same EGL/GLES drivers as for QtCompositor
> (wayland-egl platform with DRM support included). Currently this is not
> possible without hacking the co
I don't think this lengthy discussion led to any concrete answers, but I do
think that the questions are important and need such answers.
I'll try to summarize the problems that need attention:
1. screen locking
1.1 who is going to implement it: compositor/compositor plugin/app
1.2 inhibit locking
Hi,
we run Wayland on a platform without a MESA based EGL. But we still want
to run the DRM compositor and use the same EGL/GLES drivers as for
QtCompositor (wayland-egl platform with DRM support included). Currently
this is not possible without hacking the compositor removing the MESA
based c
