Bug 31799

Transforms should work.  Rotation, which uses transforms, works fine.  This might be a bug in exa or the xserver.  With the following patch:

--- a/src/r600_exa.c
+++ b/src/r600_exa.c
@@ -1231,6 +1231,8 @@ static Bool R600PrepareComposite(int op, PicturePtr pSrcPicture,
     shader_config_t vs_conf, ps_conf;
     struct r600_accel_object src_obj, mask_obj, dst_obj;
 
+    return FALSE;
+
     if (pDst->drawable.bitsPerPixel < 8 || pSrc->drawable.bitsPerPixel < 8)
        return FALSE;
 

All transforms will be done by software.  I get the same results with hardware or software.  Unfortunately, I don't have an intel system to compare with.

Well then, this is confusing. That change in r600_exa.c does not change anything in the behaviour I observe. Fact is, that

xrandr --output VGA-0 --rotate inverted

does work properly, while

xrandr --output VGA-0 --fb 1024x768 --transform 1.5,0,-280,0,1.5,0,0,0,1

does exactly nothing with the screen configuration. So we have to assume that somehow the Xorg in ubuntu is broken? Can you confirm that such a more elaborate transformation does work on r600? My actual intention was to use this for more fancy matrices like

xrandr --output VGA-0 --fb 1024x768 --transform 1.5,-0.005,-280,0,1.5,0,0,-0.00005,1

...which does scale down and applies keystone correction. Well, this stuff does work with the fglrx driver, though I observed nasty interpolation quality -- it looks better on the intel-powered laptop, by far.

Anyhow: If you can confirm that this is working with your setup, then this bug can be closed, the issue blamed on ubuntu. I will resort now to using the PCI Matrox G450 card for movies and scale down the image via non-fullscreen playback; live with the slight keystone effect and rather enjoy the tear-free video experience that sadly cannot be matched by either radeon driver since the introducton of textured video...

Hi,

I'm using an evergreen (r700?) card with a 1.9.2 xorg-server and your transformation works for me (well it screws up my screens but thats just because my screens are allready rotated etc.).

If that change from Alex do the transformation in software and even with that change transformation isn't working for you it really seems to be an ubuntu/xorg whatever issue.

Should be fixed in f074762fff4253a457cb48519bb33a2e2c90f8b9, however, it appears EXA or the xserver does the transform wrong at least on some xservers.

Hi all!
For me, on Dell 1535 notebook with RV620 (ATI Mobility Radeon HD3450), xrandr scaling does not work on LVDS output. Am I doing something wrong or does it apply to this bug?
xrandr --output LVDS --size 1920x1080 --fbmm 1920x1080 --scale 1.25x1.2 --panning 1920x1080
Changes screen size to 1920x1080, but the picture isn't scaled - only top-left 1440x900 (native res) is displayed. Transform matrix remains (1,1,1) diagonal. No errors.

Also, I can't manage to get scaling working on attached projector (VGA-0) (although this is more probably my fault - can you point to it?). I tried the following command:
xrandr --output VGA-0 --mode 1920x1080 --fbmm 1440x900 --same-as LVDS --scale 0.75x0.8 --output LVDS --size 1440x900 

I just get:
X Error of failed request:  BadMatch (invalid parameter attribute)
  Major opcode of failed request:  149 (RANDR)
  Minor opcode of failed request:  29 (RRSetPanning)
  Serial number of failed request: 32
  Current serial number in output stream: 32

Thomas Orgis, Ubuntu Maverick reached EOL on April 10, 2012. For more on this, please see https://wiki.ubuntu.com/Releases .

If this is reproducible on a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Actually, I finally fixed this recently, but forgot updating this report.

*** This bug has been marked as a duplicate of bug 80678 ***