NVIDIA Proposes "DeepColor Visual" Extension For X.Org Server, For HDR On Linux

[starshipeleven]

If you think that there'll be a general switch to Wayland any time soon, you're deluded.

haters are gonna hate.

[pal666]

wake me up when they will propose wayland extention

If you think that there'll be a general switch to Wayland any time soon, you're deluded.

if you don't know that fedora switched to wayland few releases ago, you are living under rock

[pal666]

Wikipedia says initial release was on February 9, 2012. But nice forward looking if indeed it lacks HDR support.

so 5.5 years ago, plus several years of development. nice they didn't develop for non-existing hardware?

[Luke_Wolf]

If you think that there'll be a general switch to Wayland any time soon, you're deluded.

Oh yes because Fedora hasn't switched, Ubuntu definitely won't be switching for it's next release, OpenSUSE Tumbleweed definitely doesn't default to it for GNOME, and Arch just can't have it as the GNOME default... in fact pretty much all the distros that carry GNOME definitely won't be just sticking to the upstream default of wayland...

And Plasma? well.. obviously it's not close to being ready... it's not like the upstream defaults could conceivably change in a year or two that distributions will just accept... clearly not

So obviously you're right that there won't be a general switch soon... definitely...oh wait no sorry... got that all backwards... You're wrong.

[duby229]

Oh yes because Fedora hasn't switched, Ubuntu definitely won't be switching for it's next release, OpenSUSE Tumbleweed definitely doesn't default to it for GNOME, and Arch just can't have it as the GNOME default... in fact pretty much all the distros that carry GNOME definitely won't be just sticking to the upstream default of wayland...

And Plasma? well.. obviously it's not close to being ready... it's not like the upstream defaults could conceivably change in a year or two that distributions will just accept... clearly not

So obviously you're right that there won't be a general switch soon... definitely...oh wait no sorry... got that all backwards... You're wrong.

Yay! I like it so much! It's so right -because- it's so wrong!

[TheOne]

Technically speaking, that's a compositor thing, so it's the compositor that needs to be FP16-aware and translate lower stuff to FP16, Wayland per-se is indifferent to this.
see https://wiki.gnome.org/Initiatives/HDR
and page 16 of these slides (from NVIDIA) https://www.x.org/wiki/Events/XDC201...c-2016-hdr.pdf

Wayland almost leaves all responsability to the compositor or the developers of a desktop environment, so basically they have more stuff to worry about, seeing how inconvenient wayland is been from the start isn't looking any good. Every freaking game now needs to be ported from X to wayland for it to perform well, thats sad, but ohh wayland is the magic wand to cure all our graphic issues. Weren't some guys that modified the X server to perform much better and sold it commercially, why can't the same be made in a open source matter?

[polarathene]

if you don't know that fedora switched to wayland few releases ago, you are living under rock

It's the default, doesn't meant that professional users of the distro are choosing to use it? While Gnome has support for nvidia it's still quite broken and not ready yet(I don't think Wayland is default for nvidia hardware atm), see one of the devs recent blog posts that was featured on phoronix for the F26 release if you need official confirmation of that.

Wayland still cannot handle certain use-cases as well as x11 afaik? Screen recording and VNC come to mind? Synergy for remote input also lacks Wayland support, they're working on it as many customers complain specifically about Fedora.

I'm sure there are other issues with Wayland at the moment too, these are just ones I've got personal interest in and can recall. I'm looking forward to Wayland but I don't feel it's going to be ready for another year or two, for some it'll be fine and meet their needs and that's great

Oh yes because Fedora hasn't switched, Ubuntu definitely won't be switching for it's next release, OpenSUSE Tumbleweed definitely doesn't default to it for GNOME, and Arch just can't have it as the GNOME default... in fact pretty much all the distros that carry GNOME definitely won't be just sticking to the upstream default of wayland...

And Plasma? well.. obviously it's not close to being ready... it's not like the upstream defaults could conceivably change in a year or two that distributions will just accept... clearly not

So obviously you're right that there won't be a general switch soon... definitely...oh wait no sorry... got that all backwards... You're wrong.

See the response to the previous quote.

Tumbleweed isn't Leap, nor is Fedora RHEL. Different set of users there, but worth noting that if the ones that are targeted towards enterprise/professional users(not saying TW or Fedora don't cater to them), then it just might not be as ready as you believe it is. Ubuntu isn't known for making smart decisions, no idea why you're bringing that up to support your claims.

"A general switch to Wayland" would imply DE agnostic no? Gnome seems to be the only DE you're addressing as Wayland ready(despite issues I've addressed earlier). Plasma has it's fair share of user base, they are managing to improve the Wayland experience with each release at least, and openSUSE has made it rather important for them to meet a certain level of quality for Wayland offering for an LTS release early next year. Kwin is however very firm on not supporting nvidia egl streams, so the work on whatever the other approach nvidia is discussing with the community to solve that issue will need to be done before Plasma is supporting Wayland for a good portion of users out of the box.

[carewolf]

Technically speaking, that's a compositor thing, so it's the compositor that needs to be FP16-aware and translate lower stuff to FP16, Wayland per-se is indifferent to this.
see https://wiki.gnome.org/Initiatives/HDR
and page 16 of these slides (from NVIDIA) https://www.x.org/wiki/Events/XDC201...c-2016-hdr.pdf

The fp16 part is the easy part and already possible. The problem is configuring the monitor for hybrid-log gamma negotiating application to use that colorspace and convert from sRGB if they do not.

[bug77]

Technically speaking, that's a compositor thing, so it's the compositor that needs to be FP16-aware and translate lower stuff to FP16, Wayland per-se is indifferent to this.
see https://wiki.gnome.org/Initiatives/HDR
and page 16 of these slides (from NVIDIA) https://www.x.org/wiki/Events/XDC201...c-2016-hdr.pdf

The Wayland protocol needs to be extended to define a way to attach FP16 buffers to surfaces.

There seems to be at least one bit missing from the protocol.

pal666 Colour spaces did not start with the current batch of video cards.

[carewolf]

Wikipedia says initial release was on February 9, 2012. But nice forward looking if indeed it lacks HDR support.

The Nokia N9 from 2011 was using Wayland and Qt's support for Wayland. At that point it was already 5 years old and distros had promised to switch to Wayland and then dropped it when it wasn't ready for anything beyond embedded.