[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-xorg
Subject:    Odd behavior with Radeon DRI and composite
From:       Anthony Romano <dominatus () gmail ! com>
Date:       2005-07-28 23:01:26
Message-ID: d3ca50690507281601718c8fc5 () mail ! gmail ! com
[Download RAW message or body]

I understand its not fully working yet, Im just trying to see why this is 
happening

Upon booting X with the radeon OSS driver and DRI and composite enabled, all 
is well.

If, however, I start a GL based app, like glxgears, composite slows to a 
crawl. 

If I restart xcompmgr it sometimes fixes it

If I launch the game Chromium, which uses GL it will kill the xcompmgr for 
me. If I restart it right after this game it willl *always* work just fine. 

It's as if the game "resets" the card in a way that brings it back to its 
original state when I booted X. In a way that restarting xcompmgr only 
sometimes (randomly?) does. Any explanations? Thanks!

[Attachment #3 (text/html)]

I understand its not fully working yet, Im just trying to see why this is h=
appening<br>
<br>
Upon booting X with the radeon OSS driver and DRI and composite enabled, al=
l is well.<br>
<br>
If, however, I start a GL based app, like glxgears, composite slows to a cr=
awl. <br>
<br>
If I restart xcompmgr it sometimes fixes it<br>
<br>
If I launch the game Chromium, which uses GL it will kill the xcompmgr
for me. If I restart it right after this game it willl *always* work
just fine. <br>
<br>
It's as if the game &quot;resets&quot; the card in a way that brings it bac=
k to
its original state when I booted X. In a way that restarting xcompmgr
only sometimes (randomly?) does. Any explanations? Thanks!<br>


[prev in list] [next in list] [prev in thread] [next in thread]