FaSTTUBe/GST-Tensordecoder-ov_ep
37
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

v4l2object: Update image size when extrapolating

Browse Source 
Update the image size according the amount of data we are going to
read/write. This workaround bugs in driver where the sizeimage provided
by TRY/S_FMT represent the buffer length (maximum size) rather then the expected
bytesused (buffer size).

https://bugzilla.gnome.org/show_bug.cgi?id=775564
This commit is contained in:
Nicolas Dufresne 2017-01-02 19:29:04 -05:00
parent b460f18f17
commit 0b83e4ceaf
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
sys/v4l2/gstv4l2object.c
View File

@ -2963,6 +2963,13 @@ gst_v4l2_object_extrapolate_info (GstV4l2Object * v4l2object,
"stride %d, offset %" G_GSIZE_FORMAT, i, stride, info->stride[i], "stride %d, offset %" G_GSIZE_FORMAT, i, stride, info->stride[i],
info->offset[i]); info->offset[i]);
} }
/* Update the image size according the amount of data we are going to
* read/write. This workaround bugs in driver where the sizeimage provided
* by TRY/S_FMT represent the buffer length (maximum size) rather then the expected
* bytesused (buffer size). */
if (offs < info->size)
info->size = offs;
} }
static void static void