The current state of EGL in KDE/Plasma

[Martin van Es]

Hi,

I want to raise a question about the current state of EGL in plasma? I ask,
because recenlty I've been experiencing severe instability issues using
EGL, although I was under the impression that EGL was "the way forward"?
(It turned out "Vulcan" is, but that's a different story).

After Googling around for the differences between GLX and EGL I came to the
conclusion that besides EGL being newer, it is the only road to wayland and
thus worth the switch.

https://blog.martin-graesslin.com/blog/2015/08/should-we-target-egl-as-the-default/

However, to use EGL reliably I had to enable DRI3 in my intel driver.

https://bugs.kde.org/show_bug.cgi?id=352427

This works, but results in many faced strange lockups (greeter locks up,
chrome locks up, external monitor disconnect is instable etc.).

I attributed these problems to my unresponsible need for cutting edge
plasma packages using kubuntu-backports and a composited desktop. But since
changing back to GLX/DRI2 I have yet to see any problems. My desktop is as
stable as it ever was under 4.*

In hindsight, having to deliberately enable DRI3 in xorg.conf for my intel
GPU should have been a sign on the wall that it might not be ready yet?

So, my questions are: what's KDE's offficial stand on EGL? Is Martin
(Graesslin)'s Blog still valid? Should we be worried GLX will be deprecated
before intel driver is ready for DRI3 by default? Should we worry about
wayland integration on intel hardware? Is EGL a dead end, etc. etc?

Best regards,
Martin
-- 
If 'but' was any useful, it would be a logic operator
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde/attachments/20160128/f33921f8/attachment.htm>
-------------- next part --------------
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.