[Openchrome-users] Could not lock DMA pages

[Thomas Hellström]

MagicITX wrote:

>>
>     Strange.
>
>     Tim, Can you set
>     XV_DEBUG
>     at the beginning of via_swov.h and recompile the driver, rerun and
>     post a more verbose output?
>
>     /Thomas
>
>
>>     -- 
>>
>>     Tim
>>     www.magicitx.com <http://www.magicitx.com>
>
>
>
> Here you go.  Thanks!
>
>
> -- 
>
> Tim
> www.magicitx.com <http://www.magicitx.com>

OK, There are actually three different errors involved here.
 
1) The "Could not lock dma pages" message was due to a bug in via drm, 
that requested the wrong direction protection on locked dma pages. 
Apparently vlc is the only driver that marks the image memory read-only. 
This is fixed in via drm 2.9.0. Recently checked in.

2) There were some serious XV YUY2 errors in the openchrome driver. 
These are hopefully fixed in svn revision 137, which also requests drm 
version 2.9.0 or higher to activate DMA blitting.

3) It seems that VLC doesn't format the Xv images as the X server tells 
it to do. In particular, it doesn't adhere to pitches. This makes YV12 
produce rendering errors on widths that are not multiples of 32, but 
YUY2 is OK for widths that are multiples of 16. (when dmablit is on, 
otherwise the openchrome driver requests that strides and widths are the 
same). This should really be communicated to the VLC developers.

/Thomas