>Laurent Pinchart wrote:
>On Thursday 22 April 2010 11:24:52 Pawel Osciak wrote:
>> >Laurent Pinchart wrote:
>> >> According to the V4L2 specification, applications set bytesused, field
>> >> and timestamp fields of struct v4l2_buffer when the buffer is intended
>> >> for output and memory type i
Hi Pawel,
On Thursday 22 April 2010 11:24:52 Pawel Osciak wrote:
> >Laurent Pinchart wrote:
> >> According to the V4L2 specification, applications set bytesused, field
> >> and timestamp fields of struct v4l2_buffer when the buffer is intended
> >> for output and memory type is MMAP. This adds pr
Hi Laurent,
>Laurent Pinchart wrote:
>> According to the V4L2 specification, applications set bytesused, field and
>> timestamp fields of struct v4l2_buffer when the buffer is intended for
>> output and memory type is MMAP. This adds proper copying of those values
>> to videobuf_buffer so drivers
Hi Pawel,
On Wednesday 21 April 2010 11:44:27 Pawel Osciak wrote:
> According to the V4L2 specification, applications set bytesused, field and
> timestamp fields of struct v4l2_buffer when the buffer is intended for
> output and memory type is MMAP. This adds proper copying of those values
> to vi
According to the V4L2 specification, applications set bytesused, field and
timestamp fields of struct v4l2_buffer when the buffer is intended for
output and memory type is MMAP. This adds proper copying of those values
to videobuf_buffer so drivers can use them.
Signed-off-by: Pawel Osciak
Signed