Fedora 19 Readies AMD "RadeonSI" Driver

[agd5f]

Yes, using a compositor removes tearing (assuming a proper compositor).

I happen to use X without a compositor, so tearing in "2d mode" would seriously affect me.

The only reasonable way to avoid tearing is to use a compositor.

[agd5f]

Can someone please elaborate on what the current state of GLAMOR is?
Does it support multi-monitor configurations properly (zaphod, xinerama)?
At least zaphod mode wasn't supported not long ago (don't know about xinerama).
What about screen rotations? Does it work?
!

Rotation works fine. Not sure about zaphod.

[curaga]

Hmm. Isn't that solvable with multi-buffered compositors?
At least, wasn't that the conclusion from "some other" thread?
Well, that probably adds some latency, but there is no free lunch, I guess.

I'm still eagerly waiting for information about GLAMOR's status
concerning multiple screens and screen rotations.

Yes, using a compositor removes tearing (assuming a proper compositor).

I happen to use X without a compositor, so tearing in "2d mode" would seriously affect me.

[entropy]

It still tears, I hear

Hmm. Isn't that solvable with multi-buffered compositors?
At least, wasn't that the conclusion from "some other" thread?
Well, that probably adds some latency, but there is no free lunch, I guess.

I'm still eagerly waiting for information about GLAMOR's status
concerning multiple screens and screen rotations.

[curaga]

Question is, how severe is the tearing? Is it those kind of 'temporary' tearing which disappears once you force the display to redraw the affected portion by simply moving stuff (e.g.: a window) to the tear area?

Or is it a more severe 'permanent' tearing that stays on for the entire session even after the display has been refreshed?

I can live with the first, but the second one obviously makes the display unusable.

I wouldn't call the first one tearing; that would be corruption or a failing damage/refresh call, if moving a window over it fixes it.

Tearing is an incomplete update when something changes, see this example for how horizontal tearing looks like: http://community.avid.com/cfs-filesy...ng-example.jpg

[Sonadow]

It still tears, I hear

Question is, how severe is the tearing? Is it those kind of 'temporary' tearing which disappears once you force the display to redraw the affected portion by simply moving stuff (e.g.: a window) to the tear area?

Or is it a more severe 'permanent' tearing that stays on for the entire session even after the display has been refreshed?

I can live with the first, but the second one obviously makes the display unusable.

[curaga]

Can someone please elaborate on what the current state of GLAMOR is?
Does it support multi-monitor configurations properly (zaphod, xinerama)?
At least zaphod mode wasn't supported not long ago (don't know about xinerama).
What about screen rotations? Does it work?

Thank you!

It still tears, I hear

[Drago]

Michael , can you benchmark SI. Not these multi GPU tests you were doing so far, but simple Catalyst vs Mesa with one SI card. So we can see, where Mesa is.

[entropy]

Can someone please elaborate on what the current state of GLAMOR is?
Does it support multi-monitor configurations properly (zaphod, xinerama)?
At least zaphod mode wasn't supported not long ago (don't know about xinerama).
What about screen rotations? Does it work?

Thank you!

[Ericg]

Not quite. Fedora kernel is fairly close to upstream releases and can get more than one major release because backporting security and bug fixes is too much work for Fedora kernel maintainers. KDE has one major update because it is out of sync with Fedora releases and Mesa gets backported as necessary. The general guidelines and exceptions are at

https://fedoraproject.org/wiki/Updates_Policy

Huh... Actually did not know that. I knew KDE got the one major release, I just assumed that THAT was just general policy-- N+1. Actually glad to see I was wrong thanks for the correction Rahul.