[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7c936a58-7ad9-60a5-1f4a-e86ee358752a@xs4all.nl>
Date: Fri, 28 Feb 2020 09:50:20 +0100
From: Hans Verkuil <hverkuil@...all.nl>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: 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 2/28/20 4:57 AM, Sergey Senozhatsky wrote:
> 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?
Not for the reserved field, only for the flags field.
Regards,
Hans
>
> -ss
>
Powered by blists - more mailing lists