plugins: enable memory maps for read & write.

Hence vaapisink can display buffers decoded by gst-libav, or HW decoded
buffers can be further processed in-place, e.g. with a textoverlay.

https://bugzilla.gnome.org/show_bug.cgi?id=704078

[ported to current git master branch, amended commit message]
Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
This commit is contained in:
Víctor Manuel Jáquez Leal 2013-07-12 06:34:15 -04:00 committed by Gwenole Beauchesne
parent a4d88db0fd
commit 0e87abc574

View file

@ -167,11 +167,6 @@ gst_video_meta_map_vaapi_memory (GstVideoMeta * meta, guint plane,
if (!ensure_image (mem))
goto error_ensure_image;
// Check that we can actually map the surface, or image
if ((flags & GST_MAP_READWRITE) == GST_MAP_READWRITE &&
!mem->use_direct_rendering)
goto error_unsupported_map;
// Load VA image from surface
if ((flags & GST_MAP_READ) && !mem->use_direct_rendering)
gst_vaapi_surface_get_image (mem->surface, mem->image);
@ -192,11 +187,6 @@ error_incompatible_map:
GST_ERROR ("incompatible map type (%d)", mem->map_type);
return FALSE;
}
error_unsupported_map:
{
GST_ERROR ("unsupported map flags (0x%x)", flags);
return FALSE;
}
error_ensure_surface:
{
const GstVideoInfo *const vip = mem->surface_info;