summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorU. Artie Eoff <ullysses.a.eoff@intel.com>2019-12-20 06:38:42 -0800
committerU. Artie Eoff <ullysses.a.eoff@intel.com>2019-12-20 06:38:42 -0800
commit18d1c75d1a98123549bb994113df2614655c558b (patch)
tree8d547a4b41159fd10ba45a29be96d5f9cb3d2149
parent7ce44bc3727abe231769fc7e13f6eb3abc6d9cc6 (diff)
plugins: base: do not reset can_dmabuf
Don't reset the can_dmabuf field. This restores the close/reset logic that existed prior to commit ca2942176b5632e07eebac23336954f9aaf1cb26 in regards to dmabuf support. Plugins only call gst_vaapi_plugin_base_set_srcpad_can_dmabuf once during startup, but may need to reset the other private fields multiple times during negotiation. Thus, can_dmabuf should be exempt from the resets. Fixes #208
-rw-r--r--gst/vaapi/gstvaapipluginbase.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/gst/vaapi/gstvaapipluginbase.c b/gst/vaapi/gstvaapipluginbase.c
index eba6efd7..7c167784 100644
--- a/gst/vaapi/gstvaapipluginbase.c
+++ b/gst/vaapi/gstvaapipluginbase.c
@@ -68,7 +68,6 @@ gst_vaapi_pad_private_reset (GstVaapiPadPrivate * priv)
priv->caps_is_raw = FALSE;
g_clear_object (&priv->other_allocator);
- priv->can_dmabuf = FALSE;
}
void