Le vendredi 17 avril 2015 à 15:53 +0300, Laurent Pinchart a écrit : > It's funny you mention that. I cloned the gstreamer repositories and > tried to > investigate. The gstreamer v4l2 elements started using data_offset a > year ago > in > > commit 92bdd596f2b07dbf4ccc9b8bf3d17620d44f131a > Author: Nicolas Dufresne <nicolas.dufre...@collabora.com> > Date: Fri Apr 11 17:10:11 2014 -0400 > > v4l2: Add DMABUF and USERPTR importation > > (I've CC'ed Nicolas to this e-mail) > > I'm not too familiar with the latest gstreamer code, but after a > first > investigation it seems that gstreamer uses the data_offset field for > the > purpose introduced by this patch, not to convey the header size. One > more > argument in favour of repurposing the field ;-)
My impression was that the data before the offset was non-generic and had to be skipped by applications that aren't aware. An example usage would be to a camera with custom sensor producing data serialized with the frames. The sensor data could be set in a header using custom but documented format, generic application would simply skip that and work as usual. Be aware that the implementation in GStreamer is incomplete and untested as all tested drivers where setting this offset to 0. cheers, Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
