[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200307075127.GD176460@google.com>
Date: Sat, 7 Mar 2020 16:51:27 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Hans Verkuil <hverkuil@...all.nl>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
Hans Verkuil <hans.verkuil@...co.com>,
Tomasz Figa <tfiga@...omium.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Kyungmin Park <kyungmin.park@...sung.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Sakari Ailus <sakari.ailus@....fi>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Pawel Osciak <posciak@...omium.org>,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv4 05/11] videobuf2: handle
V4L2_FLAG_MEMORY_NON_CONSISTENT flag
On (20/03/06 16:30), Hans Verkuil wrote:
[..]
> >
> > /* capabilities for struct v4l2_requestbuffers and v4l2_create_buffers */
> > @@ -2446,7 +2449,8 @@ struct v4l2_create_buffers {
> > __u32 memory;
> > struct v4l2_format format;
> > __u32 capabilities;
> > - __u32 reserved[7];
> > + __u32 flags;
>
> The new flags argument needs to be documented in the command for struct v4l2_create_buffers.
>
Will add.
-ss
Powered by blists - more mailing lists