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

When you run XWayland, does it use DRI3?
Or is this only useful when X.org runs standalone?

DRI is all about Xorg and XWayland only. Wayland doesn't NEED these extensions, its all in there already by design.

EDIT 1: DRI3 is mostly about sending buffer allocations back to the clients-- and also fixing tearing on sandy bridge / ivy bridge (yes...according to keith, the tearing on sandy bridge and ivy bridge could only be fixed by a new DRI extension)

EDIT 2: As far as XWayland is concerned... it would probably use DRI3 internally, then hand off the buffer to Wayland to be displayed. But if you're using a GTK3 or Qt5 app, thats a non-issue because they are Wayland-native anyway.

Comment

Not everything... they can't fix *everything*. All this does is prop up some of the weak areas, keeping X going a bit longer. Wayland is the long-term fix, the system designed for current and future needs, rather than the one designed in the 80s to run thin terminal servers...

Comment

Not everything... they can't fix *everything*. All this does is prop up some of the weak areas, keeping X going a bit longer. Wayland is the long-term fix, the system designed for current and future needs, rather than the one designed in the 80s to run thin terminal servers...

Michael should be putting up a Wayland article tomorrow (Thursday) or Friday in regards to fixing "everything" with X.

Comment

Wayland is the long-term fix, the system designed for current and future needs, rather than the one designed in the 80s to run thin terminal servers...

The funny part is that we're now in the 'cloud' era where everyone is going to push their processing to remote servers while displaying the results on a low-powered tablet, but apparently the future is throwing away the capability to separate the display from the software because that's a hangover from the last time we were all going to push processing to remote servers while displaying the output on low-powered hardware.

Comment

The funny part is that we're now in the 'cloud' era where everyone is going to push their processing to remote servers while displaying the results on a low-powered tablet, but apparently the future is throwing away the capability to separate the display from the software because that's a hangover from the last time we were all going to push processing to remote servers while displaying the output on low-powered hardware.

What are you talking about? Wayland only throws away the ability to send render commands over the wire to a remote server. Next to none of the commonly used X11 apps today use these APIs, they render into a buffer instead and hands that buffer to X. This is what Wayland is designed for, and making that work with a remote client is no harder than with X and should work just as well. In fact, there is already (experimental) SPICE and RDP backends for Wayland/Weston. VNC would of course also be possible.http://www.phoronix.com/scan.php?pag...tem&px=MTM0MDghttp://www.phoronix.com/scan.php?pag...tem&px=MTM1NzQ