Originally posted by mannerov
View Post
Announcement
Collapse
No announcement yet.
XWayland GLAMOR & DRI3 Support Added In Mainline X.Org Server
Collapse
X
-
-
Originally posted by jrch2k8 View Postsweet, it seems will be faster than expected , you aware if the patches will require infrastructure at kernel level(not commited yet) for drivers or gallium patches are enough?
That doesn't mean their DDX will support them though. (Nouveau DDX support it, but it is disabled for the Amd DDX).
Leave a comment:
-
Originally posted by mannerov View PostPatches to have DRI3 support for gallium drivers are soon landing in master. They are on the ml and reviewed.
Leave a comment:
-
Originally posted by uid313 View PostInteresting.
What about when GNOME supports bypass composting? (I assume it eventually will)
What about when PRESENT support is merged for XWayland? (I assume it will)
What about when comparing using DRI3 instead of DRI2?
Looks like the default with the intel DDX when vblank_mode=0 (no vsync) is to do the same thing than the Present fallback.
However it has a parameter to switch to a better mode (in my point of view) that would do flips instead of copies. That should increase performance.
Originally posted by jrch2k8 View Postthis patches only work for intel driver, gallium drivers don't have DRI3 support as far as i know, keith sent a patches some time ago for RFC but i never see them in master, so you need recent intel driver
Leave a comment:
-
Originally posted by blackout23 View PostIs anything special needed to make use of GLAMOR for Xwayland like further patches to mutter? I have built Xwayland from Kristians own Xorg branch a month ago, which already had these changes as far as I know, but in Gnome 3.12 it was still using llvmpipe for Xwayland. The mutter build I'm using is a bit old though. It's the snapshot right after Xwayland DDX support was added since the newest version of mutter don't work with the rest of Gnome 3.12.
Leave a comment:
-
Originally posted by Weegee View PostCould it be possible that nvidia releases a Wayland-compatible version of their closed source driver in conjunction with the XServer 1.16 release? If I remember correctly there was a discussion about XWayland compatibility and their driver on a mailing list a few weeks ago, I might be wrong though.
Or is XWayland support not necessary to be compatible with the 1.16 release?
Leave a comment:
-
Originally posted by mannerov View PostWithout benchmarks I can predict the results:
Gnome doesn't bypass compositing yet for fullscreen app, thus decreasing performance because of the copy done by compositing.
Present support is not merged for XWayland, thus it uses the Present fallback, which caps the number of copies it does to 60 per seconds (in contrary to dri2 with vblank_mode=0).
Thus the result is: slower for slow apps ( < 60 fps), faster for fast apps (> 60 fps), if we compare to a desktop bypassing compositing, and using dri2.
What about when GNOME supports bypass composting? (I assume it eventually will)
What about when PRESENT support is merged for XWayland? (I assume it will)
What about when comparing using DRI3 instead of DRI2?
Leave a comment:
-
Originally posted by drago01 View PostYou need mesa 10.2 and mutter 3.13.x ... 3.12 does not work with the "new" (ddx less) xwayland.
Gnome 3.12 on Wayland already is very promising. The missing mouse pointer acceleration is basically the only thing that's bugging me. Sometimes I have to click a window titlebar first before it takes any input (like gnome-terminal). Other than that I could see myself using it fulltime.
Leave a comment:
Leave a comment: