If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Comment

Just what I expected to hear: it's not out, so no plans to commit resources - that's the sane thing to do. Keeping an eye out for Wayland is also a bonus. The only thing that could become a problem is Wayland attitude towards blobs; they have ignored blobs so far. This can be justified, concentrate available resources to getting Wayland to 1.0 first, deal with non-essential features after you have a stable, solid product. Afaik, there is no info available about possible blob support. Seeing that nvidia takes Wayland seriously, let's hope the reciprocal is also true.

Comment

Just what I expected to hear: it's not out, so no plans to commit resources - that's the sane thing to do. Keeping an eye out for Wayland is also a bonus. The only thing that could become a problem is Wayland attitude towards blobs; they have ignored blobs so far. This can be justified, concentrate available resources to getting Wayland to 1.0 first, deal with non-essential features after you have a stable, solid product. Afaik, there is no info available about possible blob support. Seeing that nvidia takes Wayland seriously, let's hope the reciprocal is also true.

Wayland doesn't have a good or bad attitude towards blobs, it's about blobs not working under Wayland because they've been written to work on Unix-like systems only under X.org, hence to make the blobs work with Wayland the best way would be to implement EGL & KMS support, that is, the stuff that Wayland relies on. There's no bias nor artificial barriers.

Comment

Wayland doesn't have a good or bad attitude towards blobs, it's about blobs not working under Wayland because they've been written to work on Unix-like systems only under X.org, hence to make the blobs work with Wayland the best way would be to implement EGL & KMS support, that is, the stuff that Wayland relies on. There's no bias nor artificial barriers.

I didn't mean they were hostile or anything. Just that I'm not aware of any efforts to accommodate blobs yet and if Wayland doesn't show any interest past 1.0, this could become a problem. But as long as Wayland and others agree to tackle blob support together, we'll all be in heaven.

PS I doubt nvidia's blob was written for X.org only because it seems to be working fine on Windows, too.

Comment

I didn't mean they were hostile or anything. Just that I'm not aware of any efforts to accommodate blobs yet and if Wayland doesn't show any interest past 1.0, this could become a problem. But as long as Wayland and others agree to tackle blob support together, we'll all be in heaven.

PS I doubt nvidia's blob was written for X.org only because it seems to be working fine on Windows, too.

An X dev here in the forums stated that its easy for the blob makers to support wayland. So the problem isn't the wayland devs not wanting to support blobs.

And sure enough, absolutely nothing will work outside of FOSS-land. People will be forced to engage in all kinds of Wayland-on-X hackery to get basic functionality and the masses will avoid Linux like the plague... And where does that put companies like Valve? Questioning their priorities and commitments, probably.

Absolute nonsense.

The Wayland GL integration was in fact designed to make it as easy as possible. There's nothing Mesa-specific about it, and NVIDIA could do it quite easily today with not very much work. Certainly it would be infinitely smaller than their X driver, which is huge and spectacularly complex. They just don't want to at the moment, because the customers they care about (thousands of workstations) aren't interested right now.