[Mesa-dev] Status of VDPAU and XvMC state-trackers (was Re: Build error on current xvmc-r600 pipe-video)
alexdeucher at gmail.com
Tue Apr 26 06:52:23 PDT 2011
2011/4/26 Christian König <deathsimple at vodafone.de>:
> Hi Andy and everybody on the list,
> sorry for the late reply, but i've been on vacation the last couple of
> Am Dienstag, den 12.04.2011, 21:38 +0100 schrieb Andy Furniss:
>> In addition to the quit crash I notice that resizing will also crash.
> Should be fixed by now. I implemented most of the missing "base"
> functionality in vdpau state tracker, so video displaying should now
> work fine.
>> When testing this HD vid -
>> It played and looked OK for about 5 seconds, but then stopped and I got
>> lots of -
>> radeon_bo_fixed_map failed to map bo
>> EE radeon_bo.c:120 radeon_bo - failed to map bo
> I couldn't reproduce the error, but it sounds like a out of (video)
> memory problem to me. Please try again and see if it still crashes.
> Additional to the work on the vdpau state tracker, I've worked on the
> xvmc and general decoding stuff a bit more:
> * Added attributes for brightness, contrast, saturation, hue and
> * Got xines xxmc output plugin working with the xvmc implementation
> * Fixed the bug in the mc code that caused most of the artefacts in the
> pendulum video
> * Reorganized and cleaned up the xvmc<->driver interface so it's using
> allot less cpu power.
> * Implemented basic support for a "zscan and quantification" stage
> To sum it up: Video output of a 1920x1080 video now uses something
> around ~20% CPU time on my old test system, compared to ~50% with Xv,
> including all the nice features like overlay menu rendering for example
> (ok only working with mplayer right now, not xine).
This looks great Christian. Nice work. One quick note regarding
68cc6bc5d8b6986acc7f5780d705f4ae9be2a446, COLOR[0-7]_INFO does need a
bo. It's required since that reg has the tiling field and we need the
reloc to know if the surface is tiled or not.
More information about the mesa-dev