Whatever action is taken, it is fine for Kodi. GLX+OML_sync_control is not an option anymore because we need EGL for vaapi. But we can fall back to the invisible window for getting vsync. I never tried using EGL and GLX in the same application, different windows. Any reason why this should not work?
Rainer On Tue, Jul 12, 2016 at 12:29 PM, Daniel Vetter <daniel at ffwll.ch> wrote: > On Fri, Jun 24, 2016 at 06:55:55AM +1000, Daniel Stone wrote: > > Hi Rainer, > > > > On 24 June 2016 at 05:54, Rainer Hochecker <fernetmenta at kodi.tv> wrote: > > > I spent some time reading and investigating on this. Bear with me, I am > > > doing Kodi development in my spare time and may not be up-to-date on > all > > > platforms. Seems Wayland is much better suited to serve as reference > > > platform as X11 does. Is that correct? If so I don't request > > > OML_sync_control for EGL. Don't waste resources and let the old crap > die. > > > > I certainly think so, for a number of reasons. I don't believe X11 > > will ever be as accurate or as efficient as Wayland can be. > > Seconded. I think GLX+OML_sync_control for X11 and Wayland with EGL and > the frame timing Daniel Stone laid out (already should work in both cases) > seems like the perfect solution. > > What kind of transition plan would be reasonable? Should we start with a > printk_once to inform userspace developers that they should change their > code, and then eventually (after a few years or so) remove that ioctl? > Maybe first behind a module option? > > Who should all be on cc for such a change? > > I'd like to get this started, it'll take years no matter what ... > -Daniel > -- > Daniel Vetter > Software Engineer, Intel Corporation > http://blog.ffwll.ch > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160713/2b76e6ae/attachment-0001.html>
