vaapisink: fix initialization with "drm" display type. upstream/0.2.6+1235+g5e5d62c
authorGwenole Beauchesne <gwenole.beauchesne@intel.com>
Fri, 7 Mar 2014 16:40:34 +0000 (17:40 +0100)
committerGwenole Beauchesne <gwenole.beauchesne@intel.com>
Fri, 13 Jun 2014 15:42:35 +0000 (17:42 +0200)
commit5e5d62cac79754ba60057fc2516135aad8d7de35
tree675aad62633a6da8f60353db997d2092617a6436
parenteef863f82faa7d3559cf1071ef84ec9c866e724d
vaapisink: fix initialization with "drm" display type.

Force early initializatin of the GstVaapiDisplay so that to make sure
that the sink element display object is presented first to upstream
elements, as it will be correctly featuring the requested display type
by the user.

Otherwise, we might end up in situations where a VA/X11 display is
initialized in vaapidecode, then we try VA/DRM display in vaapisink
(as requested by the "display" property), but this would cause a failure
because we cannot acquire a DRM display that was previously acquired
through another backend (e.g. VA/X11).
gst/vaapi/gstvaapisink.c