using last gentoo-stable with git radeonhd driver&git vanilla kernel sources. urxvt goes corrupt after moving its window/working inside. changes anything urxvt configs, trying to enable/disable xcompmgr/compiz gives nothing with EXA acceleration. urxvt works fine with XAA acceleration. thats with enabled dri(xv). if disabling dri(xv) from xorg config urxvt works fine.
Created attachment 25040 [details] xorg.conf
Created attachment 25041 [details] before currupt
Created attachment 25042 [details] after corrupt
Created attachment 25043 [details] [review] xorg log
(In reply to comment #0) > changes anything urxvt configs, trying to enable/disable xcompmgr/compiz gives > nothing with EXA acceleration. > urxvt works fine with XAA acceleration. There is no XAA for r6xx and newer chips, so you probably end up with no accel or shadowfb. Also compiz requires a 3D driver which is not yet ready so it won't work at all right now.
thx =(
sry but http://wiki.x.org/wiki/radeonhd%3Ar6xx_r7xx_branch ... Current status is : * It should provide EXA acceleration, Xv acceleration. ... whats about it?
Yes, EXA and Xv are supported, but XAA is not.
http://wiki.x.org/wiki/RadeonFeature 2D Acceleration (EXA)*R700 (RHD)= DONE but what?
oh sry once more. thats bug according to supported feature EXA&XV (; and so ... for compiz/xcompmgr EXA enough. just waiting another someones answer ...
(In reply to comment #10) > oh sry once more. > thats bug according to supported feature EXA&XV (; > > and so ... for compiz/xcompmgr EXA enough. > > just waiting another someones answer ... > There are two different Xorg 2D acceleration architectures: EXA and XAA. Only EXA is supported on r6xx/r7xx hardware. compiz requires 3D (provided by a separate 3D mesa driver which is not not yet useable). compiz will not work with just EXA. xcompmgr uses render so it will work with EXA.
yeah .. yr right =) >>> xcompmgr uses render so it will work with EXA. im using only xcompmgr now ( compiz not installed ) ... and was forgotten about differences compiz/xcompmgr ... and was sayed that its same ... sry
Does this issue occur with the preferred ati driver (xf86-vide-ati)? If so, please move this to the Driver/Radeon component. Development of radeonhd has pretty much halted and development focus is on the ati driver. Please see http://www.x.org/wiki/radeonhd If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.
Closing due to lack of response. Please reopen and move to the Driver/Radeon component if this issue persists with xf86-video-ati
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.