[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200228035759.GP122464@google.com>
Date: Fri, 28 Feb 2020 12:57:59 +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: [PATCHv3 05/11] videobuf2: handle
V4L2_FLAG_MEMORY_NON_CONSISTENT flag
On (20/02/27 13:36), Hans Verkuil wrote:
[..]
> > other changes, then set ``count`` to 0, ``memory`` to
> > ``V4L2_MEMORY_MMAP`` and ``format.type`` to the buffer type.
> > * - __u32
> > - - ``reserved``\ [7]
> > + - ``flags``
> > + - Specifies additional buffer management attributes.
> > + See :ref:`memory-flags`. Old drivers and applications must set it to
> > + zero.
>
> Drop the last sentence, it's not relevant.
>
> > +
> > + * - __u32
> > + - ``reserved``\ [6]
> > - A place holder for future extensions. Drivers and applications
> > must set the array to zero.
>
> Old drivers and applications still think reserved is [7] and will zero this.
Just to make sure, does this mean that you also want me to drop the
"Drivers and applications must set the array to zero" sentence?
-ss
Powered by blists - more mailing lists