[MPlayer-users] Any way to get Xv playback without tearing on fglrx?

[Nikos Chantziaras]

Vladimir Mosgalin wrote:
> [...]
> Well actually you should try xf86-video-ati driver.. It supports xv & gl
> on x1950 already (at least rumored to do so, haven't tried it, but i'm
> planning to switch to it soon).

OK, I've completely upgraded X, kernel 2.6.26 (needed for r500 DRM) and 
xf86-video-ati 6.9.0 plus all needed dependencies (Mesa and stuff, 
including dri2).  Fortunately, the stuff is already in Gentoo's repo 
(marked as testing/unstable) so installation was automatic.

I get OK 3D support now and 2D is orders of magnitude faster than fglrx. 
  I guess that's win :)

Bad news, still tearing with videos :P  xvinfo now says:

X-Video Extension version 2.2
screen #0
   Adaptor #0: "Radeon Textured Video"
     number of ports: 16
     port base: 57
     operations supported: PutImage
     supported visuals:
       depth 24, visualID 0x21
     no port attributes defined
     maximum XvImage size: 4096 x 4096
     Number of image formats: 4
       id: 0x32595559 (YUY2)
         guid: 59555932-0000-0010-8000-00aa00389b71
         bits per pixel: 16
         number of planes: 1
         type: YUV (packed)
       id: 0x32315659 (YV12)
         guid: 59563132-0000-0010-8000-00aa00389b71
         bits per pixel: 12
         number of planes: 3
         type: YUV (planar)
       id: 0x30323449 (I420)
         guid: 49343230-0000-0010-8000-00aa00389b71
         bits per pixel: 12
         number of planes: 3
         type: YUV (planar)
       id: 0x59565955 (UYVY)
         guid: 55595659-0000-0010-8000-00aa00389b71
         bits per pixel: 16
         number of planes: 1
         type: YUV (packed)

gl doesn't work at all.  Currupted screen and mplayer says:

   do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working
   correctly.
   Try adjusting the vblank_mode configuration parameter.

The kernel says:

   [drm] Loading R500 Microcode
   [drm] Num pipes: 4
   do_IRQ: 0.84 No irq handler for vector

So I guess the open source driver is better in other areas, but still as 
crappy as fglrx in video tearing?  But I'll try tweaking some settings more.

If anyone installs this open source radeon driver and wants to test for 
tearing, here's a video that makes tearing 100% obvious (since it's 
60FPS): http://foss.math.aegean.gr/~realnc/vids/3DMark2000.mkv  That 
video is pretty much unwatchable here while it looks super-fluid in 
Windoze :-|