On 08/29/2018 06:30 AM, Tomasz Figa wrote:
> On Fri, Aug 24, 2018 at 2:33 AM Nicolas Dufresne wrote:
>>
>> Le jeudi 23 août 2018 à 10:05 +0200, Paul Kocialkowski a écrit :
>>> Hi,
>>>
>>> On Wed, 2018-08-22 at 14:33 -0300, Ezequiel Garcia wrote:
On Wed, 2018-08-22 at 16:10 +0200, Paul Kocialk
On Fri, Aug 24, 2018 at 4:30 PM Hans Verkuil wrote:
>
> On 08/23/2018 07:37 PM, Nicolas Dufresne wrote:
> > Le jeudi 23 août 2018 à 16:31 +0200, Hans Verkuil a écrit :
> >>> I propose adding these capabilities:
> >>>
> >>> #define V4L2_BUF_CAP_HAS_REQUESTS 0x0001
> >>> #define V4L2_BUF_CAP
On Fri, Aug 24, 2018 at 2:33 AM Nicolas Dufresne wrote:
>
> Le jeudi 23 août 2018 à 10:05 +0200, Paul Kocialkowski a écrit :
> > Hi,
> >
> > On Wed, 2018-08-22 at 14:33 -0300, Ezequiel Garcia wrote:
> > > On Wed, 2018-08-22 at 16:10 +0200, Paul Kocialkowski wrote:
> > > > Hi,
> > > >
> > > > On Tu
On Thu, Aug 23, 2018 at 5:05 PM Paul Kocialkowski
wrote:
>
> Hi,
>
> On Wed, 2018-08-22 at 14:33 -0300, Ezequiel Garcia wrote:
> > On Wed, 2018-08-22 at 16:10 +0200, Paul Kocialkowski wrote:
> > > Hi,
> > >
> > > On Tue, 2018-08-21 at 17:52 +0900, Tomasz Figa wrote:
> > > > Hi Hans, Paul,
> > > >
On Wed, Aug 22, 2018 at 11:10 PM Paul Kocialkowski
wrote:
>
> Hi,
>
> On Tue, 2018-08-21 at 17:52 +0900, Tomasz Figa wrote:
> > Hi Hans, Paul,
> >
> > On Mon, Aug 6, 2018 at 6:29 PM Paul Kocialkowski
> > wrote:
> > >
> > > On Mon, 2018-08-06 at 11:23 +0200, Hans Verkuil wrote:
> > > > On 08/06/20
Hi,
On Fri, 2018-08-24 at 09:29 +0200, Hans Verkuil wrote:
> On 08/23/2018 07:37 PM, Nicolas Dufresne wrote:
> > Le jeudi 23 août 2018 à 16:31 +0200, Hans Verkuil a écrit :
> > > > I propose adding these capabilities:
> > > >
> > > > #define V4L2_BUF_CAP_HAS_REQUESTS 0x0001
> > > > #defin
On 08/23/2018 07:37 PM, Nicolas Dufresne wrote:
> Le jeudi 23 août 2018 à 16:31 +0200, Hans Verkuil a écrit :
>>> I propose adding these capabilities:
>>>
>>> #define V4L2_BUF_CAP_HAS_REQUESTS 0x0001
>>> #define V4L2_BUF_CAP_REQUIRES_REQUESTS0x0002
>>> #define V4L2_BUF_CAP_HAS_M
Le jeudi 23 août 2018 à 16:31 +0200, Hans Verkuil a écrit :
> > I propose adding these capabilities:
> >
> > #define V4L2_BUF_CAP_HAS_REQUESTS 0x0001
> > #define V4L2_BUF_CAP_REQUIRES_REQUESTS0x0002
> > #define V4L2_BUF_CAP_HAS_MMAP 0x0100
> > #define V4L2_BUF_CAP_H
Le jeudi 23 août 2018 à 10:05 +0200, Paul Kocialkowski a écrit :
> Hi,
>
> On Wed, 2018-08-22 at 14:33 -0300, Ezequiel Garcia wrote:
> > On Wed, 2018-08-22 at 16:10 +0200, Paul Kocialkowski wrote:
> > > Hi,
> > >
> > > On Tue, 2018-08-21 at 17:52 +0900, Tomasz Figa wrote:
> > > > Hi Hans, Paul,
>
Hi all,
After reading through the comments I came to the following conclusions:
On 08/04/18 15:50, Hans Verkuil wrote:
> Hi all,
>
> While the Request API patch series addresses all the core API issues, there
> are some high-level considerations as well:
>
> 1) How can the application tell that
Hi all,
Based on the discussion on the mailinglist I came to the following conclusions
which I will be implementing on top of the reqv18 patches:
On 08/16/18 12:25, Hans Verkuil wrote:
> Laurent raised a few API issues/questions in his review of the documentation.
>
> I've consolidated those in
On 08/20/18 09:17, Tomasz Figa wrote:
> Hi Hans,
>
> On Fri, Aug 17, 2018 at 7:09 PM Hans Verkuil wrote:
>>
>> On 17/08/18 12:02, Tomasz Figa wrote:
>>> On Thu, Aug 16, 2018 at 8:15 PM Mauro Carvalho Chehab
>>> wrote:
Em Thu, 16 Aug 2018 12:25:25 +0200
Hans Verkuil escreveu:
Hi,
On Wed, 2018-08-22 at 14:33 -0300, Ezequiel Garcia wrote:
> On Wed, 2018-08-22 at 16:10 +0200, Paul Kocialkowski wrote:
> > Hi,
> >
> > On Tue, 2018-08-21 at 17:52 +0900, Tomasz Figa wrote:
> > > Hi Hans, Paul,
> > >
> > > On Mon, Aug 6, 2018 at 6:29 PM Paul Kocialkowski
> > > wrote:
> > >
Le mercredi 22 août 2018 à 16:52 +0200, Paul Kocialkowski a écrit :
> Hi,
>
> On Wed, 2018-08-15 at 09:57 -0400, Nicolas Dufresne wrote:
> > Le lundi 06 août 2018 à 10:16 +0200, Paul Kocialkowski a écrit :
> > > Hi Hans and all,
> > >
> > > On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
>
On Wed, 2018-08-22 at 16:10 +0200, Paul Kocialkowski wrote:
> Hi,
>
> On Tue, 2018-08-21 at 17:52 +0900, Tomasz Figa wrote:
> > Hi Hans, Paul,
> >
> > On Mon, Aug 6, 2018 at 6:29 PM Paul Kocialkowski
> > wrote:
> > >
> > > On Mon, 2018-08-06 at 11:23 +0200, Hans Verkuil wrote:
> > > > On 08/06/
Hi,
On Wed, 2018-08-15 at 09:57 -0400, Nicolas Dufresne wrote:
> Le lundi 06 août 2018 à 10:16 +0200, Paul Kocialkowski a écrit :
> > Hi Hans and all,
> >
> > On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
> > > Hi all,
> > >
> > > While the Request API patch series addresses all the cor
Hi,
On Tue, 2018-08-21 at 17:52 +0900, Tomasz Figa wrote:
> Hi Hans, Paul,
>
> On Mon, Aug 6, 2018 at 6:29 PM Paul Kocialkowski
> wrote:
> >
> > On Mon, 2018-08-06 at 11:23 +0200, Hans Verkuil wrote:
> > > On 08/06/2018 11:13 AM, Paul Kocialkowski wrote:
> > > > Hi,
> > > >
> > > > On Mon, 201
On Wed, Aug 22, 2018 at 10:21 PM Paul Kocialkowski
wrote:
>
> Hi,
>
> [...]
>
> On Wed, 2018-08-15 at 14:51 +0200, Maxime Jourdan wrote:
> > Hi Paul, I think we need to go deeper than just exposing the supported
> > profiles/levels and also include a way to query the CAPTURE pixel
> > formats that
Hi,
[...]
On Wed, 2018-08-15 at 14:51 +0200, Maxime Jourdan wrote:
> Hi Paul, I think we need to go deeper than just exposing the supported
> profiles/levels and also include a way to query the CAPTURE pixel
> formats that are supported for each profile.
>
> Maybe HEVC Main produces yuv420p but
On Tue, Aug 21, 2018 at 6:15 PM Tomasz Figa wrote:
>
> On Wed, Aug 15, 2018 at 11:18 PM Hans Verkuil wrote:
> >
> > On 15/08/18 14:11, Mauro Carvalho Chehab wrote:
> > > Em Sat, 4 Aug 2018 15:50:04 +0200
> > > Hans Verkuil escreveu:
> > >
> > >> Hi all,
> > >>
> > >> While the Request API patch
On Tue, Aug 21, 2018 at 7:00 PM Sakari Ailus wrote:
>
> On Fri, Aug 17, 2018 at 12:09:40PM +0200, Hans Verkuil wrote:
> > On 17/08/18 12:02, Tomasz Figa wrote:
> > > On Thu, Aug 16, 2018 at 8:15 PM Mauro Carvalho Chehab
> > > wrote:
> > >>
> > >> Em Thu, 16 Aug 2018 12:25:25 +0200
> > >> Hans Ver
On Fri, Aug 17, 2018 at 12:09:40PM +0200, Hans Verkuil wrote:
> On 17/08/18 12:02, Tomasz Figa wrote:
> > On Thu, Aug 16, 2018 at 8:15 PM Mauro Carvalho Chehab
> > wrote:
> >>
> >> Em Thu, 16 Aug 2018 12:25:25 +0200
> >> Hans Verkuil escreveu:
> >>
> >>> Laurent raised a few API issues/questions
On Mon, Aug 6, 2018 at 5:32 PM Hans Verkuil wrote:
>
> On 08/06/2018 10:16 AM, Paul Kocialkowski wrote:
> > Hi Hans and all,
> >
> > On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
> >> Hi all,
> >>
> >> While the Request API patch series addresses all the core API issues, there
> >> are so
On Wed, Aug 15, 2018 at 11:18 PM Hans Verkuil wrote:
>
> On 15/08/18 14:11, Mauro Carvalho Chehab wrote:
> > Em Sat, 4 Aug 2018 15:50:04 +0200
> > Hans Verkuil escreveu:
> >
> >> Hi all,
> >>
> >> While the Request API patch series addresses all the core API issues, there
> >> are some high-level
Hi Hans, Paul,
On Mon, Aug 6, 2018 at 6:29 PM Paul Kocialkowski
wrote:
>
> On Mon, 2018-08-06 at 11:23 +0200, Hans Verkuil wrote:
> > On 08/06/2018 11:13 AM, Paul Kocialkowski wrote:
> > > Hi,
> > >
> > > On Mon, 2018-08-06 at 10:32 +0200, Hans Verkuil wrote:
> > > > On 08/06/2018 10:16 AM, Paul
Hi Hans,
On Thu, Aug 16, 2018 at 12:25:25PM +0200, Hans Verkuil wrote:
> Laurent raised a few API issues/questions in his review of the documentation.
>
> I've consolidated those in this RFC. I would like to know what others think
> and if I should make changes.
>
> 1) Should you be allowed to s
Hi Hans,
On Fri, Aug 17, 2018 at 7:09 PM Hans Verkuil wrote:
>
> On 17/08/18 12:02, Tomasz Figa wrote:
> > On Thu, Aug 16, 2018 at 8:15 PM Mauro Carvalho Chehab
> > wrote:
> >>
> >> Em Thu, 16 Aug 2018 12:25:25 +0200
> >> Hans Verkuil escreveu:
> >>
[snip]
> >>> 3) Calling VIDIOC_G_EXT_CTRLS fo
Em Fri, 17 Aug 2018 12:09:40 +0200
Hans Verkuil escreveu:
> On 17/08/18 12:02, Tomasz Figa wrote:
> > On Thu, Aug 16, 2018 at 8:15 PM Mauro Carvalho Chehab
> > wrote:
> >>
> >> Em Thu, 16 Aug 2018 12:25:25 +0200
> >> Hans Verkuil escreveu:
> >>
> >>> Laurent raised a few API issues/question
On 17/08/18 12:02, Tomasz Figa wrote:
> On Thu, Aug 16, 2018 at 8:15 PM Mauro Carvalho Chehab
> wrote:
>>
>> Em Thu, 16 Aug 2018 12:25:25 +0200
>> Hans Verkuil escreveu:
>>
>>> Laurent raised a few API issues/questions in his review of the
>>> documentation.
>>>
>>> I've consolidated those in th
On Thu, Aug 16, 2018 at 8:15 PM Mauro Carvalho Chehab
wrote:
>
> Em Thu, 16 Aug 2018 12:25:25 +0200
> Hans Verkuil escreveu:
>
> > Laurent raised a few API issues/questions in his review of the
> > documentation.
> >
> > I've consolidated those in this RFC. I would like to know what others think
Em Thu, 16 Aug 2018 12:25:25 +0200
Hans Verkuil escreveu:
> Laurent raised a few API issues/questions in his review of the documentation.
>
> I've consolidated those in this RFC. I would like to know what others think
> and if I should make changes.
>
> 1) Should you be allowed to set controls
Laurent raised a few API issues/questions in his review of the documentation.
I've consolidated those in this RFC. I would like to know what others think
and if I should make changes.
1) Should you be allowed to set controls directly if they are also used in
requests? Right now this is allowed
Le mercredi 15 août 2018 à 09:11 -0300, Mauro Carvalho Chehab a écrit :
> Em Sat, 4 Aug 2018 15:50:04 +0200
> Hans Verkuil escreveu:
>
> > Hi all,
> >
> > While the Request API patch series addresses all the core API
> > issues, there
> > are some high-level considerations as well:
> >
> > 1) H
Le samedi 04 août 2018 à 15:50 +0200, Hans Verkuil a écrit :
> Hi all,
>
> While the Request API patch series addresses all the core API issues, there
> are some high-level considerations as well:
>
> 1) How can the application tell that the Request API is supported and for
>which buffer type
On 15/08/18 14:11, Mauro Carvalho Chehab wrote:
> Em Sat, 4 Aug 2018 15:50:04 +0200
> Hans Verkuil escreveu:
>
>> Hi all,
>>
>> While the Request API patch series addresses all the core API issues, there
>> are some high-level considerations as well:
>>
>> 1) How can the application tell that the
On 06/08/18 10:16, Paul Kocialkowski wrote:
> Hi Hans and all,
>
> On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
>> Hi all,
>>
>> While the Request API patch series addresses all the core API issues, there
>> are some high-level considerations as well:
>>
>> 1) How can the application tel
Le lundi 06 août 2018 à 10:16 +0200, Paul Kocialkowski a écrit :
> Hi Hans and all,
>
> On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
> > Hi all,
> >
> > While the Request API patch series addresses all the core API issues, there
> > are some high-level considerations as well:
> >
> > 1
2018-08-06 11:13 GMT+02:00 Paul Kocialkowski :
> Hi,
>
> On Mon, 2018-08-06 at 10:32 +0200, Hans Verkuil wrote:
>> On 08/06/2018 10:16 AM, Paul Kocialkowski wrote:
>> > On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
>> > > Regarding point 3: I think this should be documented next to the pix
Em Sat, 4 Aug 2018 15:50:04 +0200
Hans Verkuil escreveu:
> Hi all,
>
> While the Request API patch series addresses all the core API issues, there
> are some high-level considerations as well:
>
> 1) How can the application tell that the Request API is supported and for
>which buffer types
On 4 August 2018 at 10:50, Hans Verkuil wrote:
> Hi all,
>
> While the Request API patch series addresses all the core API issues, there
> are some high-level considerations as well:
>
> 1) How can the application tell that the Request API is supported and for
>which buffer types (capture/outp
On Mon, 2018-08-06 at 11:23 +0200, Hans Verkuil wrote:
> On 08/06/2018 11:13 AM, Paul Kocialkowski wrote:
> > Hi,
> >
> > On Mon, 2018-08-06 at 10:32 +0200, Hans Verkuil wrote:
> > > On 08/06/2018 10:16 AM, Paul Kocialkowski wrote:
> > > > On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
> >
On 08/06/2018 11:13 AM, Paul Kocialkowski wrote:
> Hi,
>
> On Mon, 2018-08-06 at 10:32 +0200, Hans Verkuil wrote:
>> On 08/06/2018 10:16 AM, Paul Kocialkowski wrote:
>>> On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
Regarding point 3: I think this should be documented next to the pix
Hi,
On Mon, 2018-08-06 at 10:32 +0200, Hans Verkuil wrote:
> On 08/06/2018 10:16 AM, Paul Kocialkowski wrote:
> > On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
> > > Regarding point 3: I think this should be documented next to the pixel
> > > format. I.e.
> > > the MPEG-2 Slice format us
On 08/06/2018 10:16 AM, Paul Kocialkowski wrote:
> Hi Hans and all,
>
> On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
>> Hi all,
>>
>> While the Request API patch series addresses all the core API issues, there
>> are some high-level considerations as well:
>>
>> 1) How can the applicatio
Hi Hans and all,
On Sat, 2018-08-04 at 15:50 +0200, Hans Verkuil wrote:
> Hi all,
>
> While the Request API patch series addresses all the core API issues, there
> are some high-level considerations as well:
>
> 1) How can the application tell that the Request API is supported and for
>which
Hi all,
While the Request API patch series addresses all the core API issues, there
are some high-level considerations as well:
1) How can the application tell that the Request API is supported and for
which buffer types (capture/output) and pixel formats?
2) How can the application tell if t
On 05/25/2018 05:26 PM, Hans Verkuil wrote:
> On 25/05/18 16:16, Sakari Ailus wrote:
>> Hi Hans,
>>
>> On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote:
>>> Memory-to-memory devices have one video node, one internal control handler
>>> but two vb2_queues (DMA engines). While often there
On 25/05/18 16:16, Sakari Ailus wrote:
> Hi Hans,
>
> On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote:
>> Memory-to-memory devices have one video node, one internal control handler
>> but two vb2_queues (DMA engines). While often there is one buffer produced
>> for every buffer consum
On Fri, May 25, 2018 at 11:17 PM Sakari Ailus
wrote:
> Hi Hans,
> On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote:
> > Memory-to-memory devices have one video node, one internal control
handler
> > but two vb2_queues (DMA engines). While often there is one buffer
produced
> > for ev
Hi Hans,
On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote:
> Memory-to-memory devices have one video node, one internal control handler
> but two vb2_queues (DMA engines). While often there is one buffer produced
> for every buffer consumed, but this is by no means standard. E.g.
> de
On Thu, May 24, 2018 at 5:44 PM Hans Verkuil wrote:
> Memory-to-memory devices have one video node, one internal control handler
> but two vb2_queues (DMA engines). While often there is one buffer produced
> for every buffer consumed, but this is by no means standard. E.g.
deinterlacers
> will pr
Memory-to-memory devices have one video node, one internal control handler
but two vb2_queues (DMA engines). While often there is one buffer produced
for every buffer consumed, but this is by no means standard. E.g. deinterlacers
will produce on buffer for every two buffers consumed. Codecs that re
On Fri, Mar 23, 2018 at 6:33 PM, Sakari Ailus wrote:
>> >>> An alternative, maybe a bit crazy, idea would be to allow adding
>> >>> MEDIA_REQUEST_IOC_QUEUE ioctl to the request itself. This would be
>> >>> similar to the idea of indirect command buffers in the graphics (GPU)
>> >>> land. It could
Hi Hans and Tomasz,
On Fri, Mar 23, 2018 at 08:38:54AM +0100, Hans Verkuil wrote:
...
> >>>
> >>> Perhaps we need to consider few separate cases here:
> >>>
> >>> 1) Query control value within a request. Would return the value that
> >>> was earlier set to that particular request (and maybe -EBUS
On 03/23/2018 05:02 AM, Tomasz Figa wrote:
> On Fri, Mar 23, 2018 at 1:28 AM, Hans Verkuil wrote:
>> On 03/22/18 15:47, Tomasz Figa wrote:
>>> Hi Hans,
>>>
>>> On Thu, Mar 22, 2018 at 11:18 PM, Hans Verkuil wrote:
Requests only contain the changes since the previously queued request
On Fri, Mar 23, 2018 at 1:28 AM, Hans Verkuil wrote:
> On 03/22/18 15:47, Tomasz Figa wrote:
>> Hi Hans,
>>
>> On Thu, Mar 22, 2018 at 11:18 PM, Hans Verkuil wrote:
>>>
>>>Requests only contain the changes since the previously queued request or
>>>since the current hardware state if no ot
Le jeudi 22 mars 2018 à 18:22 +0100, Hans Verkuil a écrit :
> On 03/22/2018 05:36 PM, Nicolas Dufresne wrote:
> > Le jeudi 22 mars 2018 à 15:18 +0100, Hans Verkuil a écrit :
> > > RFC Request API
> > > ---
> > >
> > > This document
On 03/22/2018 05:36 PM, Nicolas Dufresne wrote:
> Le jeudi 22 mars 2018 à 15:18 +0100, Hans Verkuil a écrit :
>> RFC Request API
>> ---
>>
>> This document proposes the public API for handling requests.
>>
>> There has been some confusion about
Le jeudi 22 mars 2018 à 15:18 +0100, Hans Verkuil a écrit :
> RFC Request API
> ---
>
> This document proposes the public API for handling requests.
>
> There has been some confusion about how to do this, so this summarizes the
> current approach based on c
On 03/22/18 15:47, Tomasz Figa wrote:
> Hi Hans,
>
> On Thu, Mar 22, 2018 at 11:18 PM, Hans Verkuil wrote:
>> RFC Request API
>> ---
>>
>> This document proposes the public API for handling requests.
>>
>> There has been some confusion
On Thu, Mar 22, 2018 at 11:47 PM, Tomasz Figa wrote:
> Hi Hans,
>
> On Thu, Mar 22, 2018 at 11:18 PM, Hans Verkuil wrote:
>> - If due to performance reasons we will have to allocate/queue/reinit
>> multiple
>> requests with a single ioctl, then we will have to add new ioctls to the
>> media
Hi Hans,
On Thu, Mar 22, 2018 at 11:18 PM, Hans Verkuil wrote:
> RFC Request API
> ---
>
> This document proposes the public API for handling requests.
>
> There has been some confusion about how to do this, so this summarizes the
> current approach based on c
RFC Request API
---
This document proposes the public API for handling requests.
There has been some confusion about how to do this, so this summarizes the
current approach based on conversations with the various stakeholders today
(Sakari, Alexandre Courbot, Tomasz Figa and myself
63 matches
Mail list logo
