v4l2sink: don't render preroll buffers

Most v4l2 drivers will get upset when you queue the same buffer twice in a
row without first dequeueing it.

Rendering of pre-roll buffers can be re-introduced later, but will require
tracking the state of the buffer, and avoiding to re-QBUF if the buffer has
already been passed to the driver.
This commit is contained in:
Rob Clark 2010-04-04 06:23:31 -05:00
parent 48a8b53bdd
commit e24cfa7250

View file

@ -249,7 +249,6 @@ gst_v4l2sink_class_init (GstV4l2SinkClass * klass)
basesink_class->get_caps = GST_DEBUG_FUNCPTR (gst_v4l2sink_get_caps);
basesink_class->set_caps = GST_DEBUG_FUNCPTR (gst_v4l2sink_set_caps);
basesink_class->buffer_alloc = GST_DEBUG_FUNCPTR (gst_v4l2sink_buffer_alloc);
basesink_class->preroll = GST_DEBUG_FUNCPTR (gst_v4l2sink_show_frame);
basesink_class->render = GST_DEBUG_FUNCPTR (gst_v4l2sink_show_frame);
}