<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Julien,<div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Dec 8, 2015, at 12:53 AM, Julien Isorce <<a href="mailto:julien.isorce@gmail.com" class="">julien.isorce@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class="">Hi Sean,<br class=""><br class=""></div>Note that this patch "<span class="">driver_name_map</span>: <span class="">add</span> <span class="">nouveau</span> and <span class="">radeon</span> for <span class="">Mesa</span> <span class="">Gallium</span>" is only for VA_DISPLAY_DRM case.<br class=""></div></div></div></div></div></div></div></blockquote><div><br class=""></div><div><br class=""></div><div>Understood.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><br class=""></div>About your question, all patches regarding gallium backend for vaapi have landed: <a href="http://cgit.freedesktop.org/mesa/mesa/log/src/gallium/state_trackers/va" target="_blank" class="">http://cgit.freedesktop.org/mesa/mesa/log/src/gallium/state_trackers/va</a><br class=""><br class=""></div>But there are still 4 patches for nouveau driver under review, to support chunk decoding: <a href="https://github.com/CapOM/mesa/commits/st_va_nouveau_chunk_decoding" class="">https://github.com/CapOM/mesa/commits/st_va_nouveau_chunk_decoding</a><br class=""></div></div></div></div></div></blockquote><div><br class=""></div><div><br class=""></div>Thanks.  I can now track them.</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><br class=""></div><div class="">I have only tested with Nvidia hardware (with nouveau driver so), with <a href="https://github.com/mpv-player/mpv" class="">https://github.com/mpv-player/mpv</a> player and gstreamer-vaapi on videos available here: <br class=""><a href="http://download.blender.org/peach/bigbuckbunny_movies/" rel="noreferrer" target="_blank" class="">http://download.blender.org/peach/bigbuckbunny_movies/</a><br class="">
<a href="http://playready.directtaps.net/smoothstreaming/" rel="noreferrer" target="_blank" class="">http://playready.directtaps.net/smoothstreaming/</a><br class="">
<a href="https://github.com/malek0512/PLS/raw/master/Tests/centaur_2.mpg" rel="noreferrer" target="_blank" class="">https://github.com/malek0512/PLS/raw/master/Tests/centaur_2.mpg</a><br class=""><a href="http://www.h264info.com/clips.html" rel="noreferrer" target="_blank" class="">http://www.h264info.com/clips.html</a><br class=""></div><div class=""><br class=""></div>At least for radeon it is already ready, the gallium backend for vaapi is what AMD support and maintain. Maybe they also use the bridge <a href="http://cgit.freedesktop.org/vaapi/vdpau-driver" target="_blank" class="">http://cgit.freedesktop.org/vaapi/vdpau-driver</a> for some comparisons. Christian would be able to give more details about it. But in long terms I think this bridge will be only used by the Nvidia proprietary driver (unless they decide to provide a vaapi backend too)<br class=""></div></div></div></div></blockquote><div><br class=""></div><div><br class=""></div><div>I’m happy to add both to the backend, but I would like Christian to comment if he has any concerns from a radeon perspective.</div><div><br class=""></div><div>Thanks,</div><div><br class=""></div><div>Sean</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><br class=""></div>Regards<br class=""></div>Julien<br class=""><div class=""><div class=""><div class=""><br class=""><div class=""><br class=""></div></div></div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On 3 December 2015 at 22:37, Sean V Kelley <span dir="ltr" class=""><<a href="mailto:seanvk@posteo.de" target="_blank" class="">seanvk@posteo.de</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Julien,<br class="">
<span class=""><br class="">
On 11/27/2015 12:53 AM, Julien Isorce wrote:<br class="">
> This patch allows va_getDriverName to succeed. It is useful in<br class="">
> vaInitialize to select the vaapi driver provided by Mesa Gallium:<br class="">
> lib/dri/gallium_drv_video.so<br class="">
><br class="">
> Signed-off-by: Julien Isorce <<a href="mailto:j.isorce@samsung.com" class="">j.isorce@samsung.com</a>> ---<br class="">
> va/drm/va_drm_utils.c | 2 ++ 1 file changed, 2 insertions(+)<br class="">
<br class="">
</span>Can you provide a status on the Gallium patch series, have they been<br class="">
merged?  What testing have you done with the gallium backend enabled?<br class="">
<br class="">
Thanks,<br class="">
<br class="">
Sean<br class="">
<span class="im HOEnZb"><br class="">
<br class="">
><br class="">
> diff --git a/va/drm/va_drm_utils.c b/va/drm/va_drm_utils.c index<br class="">
> 71091fd..041be79 100644 --- a/va/drm/va_drm_utils.c +++<br class="">
> b/va/drm/va_drm_utils.c @@ -41,6 +41,8 @@ static const struct<br class="">
> driver_name_map g_driver_name_map[] = { { "pvrsrvkm",   8, "pvr"<br class="">
> }, // Intel UMG PVR driver { "emgd",       4, "emgd"   }, // Intel<br class="">
> ECG PVR driver { "hybrid",     6, "hybrid" }, // Intel OTC Hybrid<br class="">
> driver +    { "nouveau",    7, "gallium" }, // Mesa Gallium driver<br class="">
> +    { "radeon",     6, "gallium" }, // Mesa Gallium driver { NULL,<br class="">
> } };<br class="">
><br class="">
><br class="">
</span><div class="HOEnZb"><div class="h5">_______________________________________________<br class="">
Libva mailing list<br class="">
<a href="mailto:Libva@lists.freedesktop.org" class="">Libva@lists.freedesktop.org</a><br class="">
<a href="http://lists.freedesktop.org/mailman/listinfo/libva" rel="noreferrer" target="_blank" class="">http://lists.freedesktop.org/mailman/listinfo/libva</a><br class="">
</div></div></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></body></html>