X.Org Server 1.20 Release Candidate Due For Release Tomorrow

[phoronix]

Phoronix: X.Org Server 1.20 Release Candidate Due For Release Tomorrow

Indeed it turns out that the landing today of RandR leases and deep color / color depth 30 support for GLAMOR/modesetting is because Red Hat's Adam Jackson is finally wrangling the xorg-server 1.20 release together...

http://www.phoronix.com/scan.php?page=news_item&px=Xorg-Server-1.20-Tomorrow

[cybertraveler]

Good ol' faithful X! Glad they're keeping it ticking over. We'll need it for a while longer.

[dungeon]

He hasn't commented when he plans to issue the final release, but it will hopefully be just a matter of weeks now once the RC1 release is made.

According to history once first release candidate appear it is just a matter of months (2+ months) when actual release might happen

[boxie]

"He's still planning to accept XWayland EGLStreams support for NVIDIA, DRI3 v1.2, DMA fences support for DRI3, and per-window page-flipping for XWayland. ¨

More wayland and proprietary bloatware to X.

of all the problems with X, bloat is the problem you are singling out?

[oiaohm]

"He's still planning to accept XWayland EGLStreams support for NVIDIA, DRI3 v1.2, DMA fences support for DRI3, and per-window page-flipping for XWayland. ¨

More wayland and proprietary bloatware to X.

We need more information on why accepting EGLStreams. If this is path to using X11 modesetting driver for everything this could be worth it. Basically XWayland + EGLStreams for now but in future modesetting driver + EGLStreams with no closed source Nvidia module load. Then hopefully in the end deprecate EGLStreams as well.

So long term EGLStreams could be less proprietary bloatware to X.

The reality here is X11 as default interface is on the way out. But it going to be around for a while so it going to be how to reduce it maintenance cost over time.

[dungeon]

"He's still planning to accept XWayland EGLStreams support for NVIDIA, DRI3 v1.2, DMA fences support for DRI3, and per-window page-flipping for XWayland. ¨

More wayland and proprietary bloatware to X.

I don't see bloatware there, just disable xwayland at compile time and that is it And disable DRI3 if you don't use it, even disable glx if you don't want to use GL... it is up to you, what you want and what your drivers wants Now, your amdgpu drivers expects glx/dri/glamor combo of course, you can even disable composite, but your DE might expect that and if not yours then someone elses will, etc... You can compile mini X, just like you can do mini kernel exactly for your machine and your preferred use case

Of course major distros will continue to enable more and more bloatware everywhere as wide range of usability is The Trend

Same way you can use Wayland without X at all, it is just that there are so much apps for X so XWayland layer is needed for Wayland user pleasure... from that POV - it is better to have something than nothing albeit somewhat degraded performance expectance

[Leopard]

I don't see bloatware there, just disable xwayland at compile time and that is it And disable DRI3 if you don't use it, even disable glx if you don't want to use GL... it is up to you, what you want and what your drivers wants Now, your amdgpu drivers expects glx/dri/glamor combo of course, you can even disable composite, but your DE might expect that and if not yours then someone elses will, etc... You can compile mini X, just like you can do mini kernel exactly for your machine and your preferred use case

Of course major distros will continue to enable more and more bloatware everywhere as wide range of usability is The Trend

Same way you can use Wayland without X at all, it is just that there are so much apps for X so XWayland layer is needed for Wayland user pleasure... from that POV - it is better to have something than nothing

[dungeon]

Every number is normal, if you won't try to exceed KMS and Composite limits

[Zoll]

Isn't this release for VR to work properly with HTC Vive? i.e. to be recognized not as an additional display device but as a special class of display devices?

[beniwtv]

Isn't this release for VR to work properly with HTC Vive? i.e. to be recognized not as an additional display device but as a special class of display devices?

It already works properly - but yes, this release will allow for direct mode support, so that we can have less latency and get the DE's compositor out of the way that could be limiting FPS of the display. (In fact currently I need to use a DE where you can disable compositing).