Search:

Not necessarily, on both counts:

With the scanline wait, there can still be a tearing effect between different parts of the screen which are updated separately.

Also, the scanline wait stalls...

Exactly, there is no way to completely avoid tearing without some form of compositing. So 'no tearing' and 'no compositing' are conflicting requirements.

Yes. BTW, EXA also tears without Option "EXAVsync", but it's less annoying there because the tearing is only horizontal, not also diagonal. The best chance for a tear-free desktop would be using an...

Which specific games did you find it to be 'complete crap' for? Did you file bugs?

From the article:



Michael, will you please stop repeating this lie?

OpenGL 2.1 functionality is shaping up pretty nicely in radeonsi for the Mesa 9.1 release. Over the last couple of days,...

For accelerated GLX/X11 client rendering, yes.


Wayland doesn't provide any rendering APIs. The compositing works the same way, but the X window contents are rendered in software with...

gnome-shell works perfectly. Not sure about Quake 3 specifically right now, but it's running similar games fine.



Hasn't been for quite a long time.

Looks like it's not picking up Option "AccelMethod" "glamor". I think maybe the xorg.conf.d/ snippets must be named *.conf, or it might be easier to just put it in /etc/X11/xorg.conf.

BTW, this...

Michael, when was the last time you actually tried out radeonsi?

As I pointed out in the discussion of the previous article, it runs many real 3D apps fine now.

In fact, it would be great if...

FWIW, radeonsi can handle much more than 'some basic 3D demos' now. It runs many real games / apps fine. 3D apps run at full acceleration including page flipping. We're very close to enabling full...

Meanwhile, the draw module would offer at least an interim solution. Same for some other less popular OpenGL features, it should be possible to achieve correctness without any software rasterization...

Which driver(s) are you referring to? The only one I can think of offhand matching your description would be intel, the developers of which indeed haven't cared much about support for older servers....

In other words, out of tree drivers will be second class citizens at best (though when the people proposing this change mention what they might do with the in-tree drivers, I'm hardly hoping for the...

It's probably due to partial screen updates. Even if tearing is avoided for each individual rectangle being updated, there can still be a tearing effect between rectangles.

That's exactly why there's less difference with the Intel drivers: they're still using GEM/DRI2 with UMS.

Are you going to propose such changes on the mesa3d-dev list?

That may sometimes be the case (for minimalistic drivers ;), plus there's always a little glue code needed (in what's called 'the winsys' for historical reasons). However, adding support for a...

What makes you think it isn't working yet?

Does

Option "EXAOptimizeMigration" "off"

help with EXA?

This is a new low in Phoronix sensationalism. :( Did you forget about your own articles about the nouveau, radeon and via drivers using TTM?