Em Wed, 11 Oct 2017 01:18:58 +0300
Sakari Ailus escreveu:
> > So, if you look, for example, at the chapter 1 name:
> > "common API elements"
> >
> > it implies that every single V4L2 device node supports what's there.
> > But that's not the case, for example, for what's
Hi Mauro,
On Tue, Oct 10, 2017 at 09:49:38AM -0300, Mauro Carvalho Chehab wrote:
> Em Tue, 10 Oct 2017 14:54:35 +0300
> Sakari Ailus escreveu:
>
> > On Tue, Oct 10, 2017 at 06:15:03AM -0300, Mauro Carvalho Chehab wrote:
> > > Em Fri, 6 Oct 2017 14:51:06 +0300
> > > Sakari
Em Tue, 10 Oct 2017 14:54:35 +0300
Sakari Ailus escreveu:
> On Tue, Oct 10, 2017 at 06:15:03AM -0300, Mauro Carvalho Chehab wrote:
> > Em Fri, 6 Oct 2017 14:51:06 +0300
> > Sakari Ailus escreveu:
> >
> > > Hi Mauro,
> > >
> > > On Fri, Oct 06, 2017
On Tue, Oct 10, 2017 at 06:15:03AM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 6 Oct 2017 14:51:06 +0300
> Sakari Ailus escreveu:
>
> > Hi Mauro,
> >
> > On Fri, Oct 06, 2017 at 01:22:29PM +0300, Sakari Ailus wrote:
> > > > +V4L2 device node
> > > > + A device
Em Fri, 6 Oct 2017 14:51:06 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> On Fri, Oct 06, 2017 at 01:22:29PM +0300, Sakari Ailus wrote:
> > > +V4L2 device node
> > > + A device node that is associated to a V4L2 main driver,
> > > + as specified in
On Tue, Oct 10, 2017 at 05:30:04AM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 6 Oct 2017 13:22:29 +0300
> Sakari Ailus escreveu:
>
> > > +Bridge driver
> > > + The same as V4L2 main driver.
> >
> > Not all V4L2 main drivers can be bridge drivers. Mem-to-mem
Em Fri, 6 Oct 2017 13:22:29 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> Thanks for continuing the work on this!
>
> On Wed, Sep 27, 2017 at 07:23:43PM -0300, Mauro Carvalho Chehab wrote:
> > Add a glossary of terms for V4L2, as several concepts are complex
> > enough to
Em Tue, 10 Oct 2017 10:27:12 +0200
Hans Verkuil escreveu:
> > +V4L2 sub-device driver
> > + Part of the media hardware that implements support for
> > + a hardware component.
>
> The description now no longer fits the term. I suggest:
>
> "The V4L2 driver that
Em Fri, 6 Oct 2017 13:22:29 +0300
Sakari Ailus escreveu:
> > +Bridge driver
> > + The same as V4L2 main driver.
>
> Not all V4L2 main drivers can be bridge drivers. Mem-to-mem devices, for
> instance. How about:
>
> A driver for a device receiving image data from
On 10/10/2017 10:20 AM, Mauro Carvalho Chehab wrote:
> Em Tue, 10 Oct 2017 09:47:13 +0200
> Hans Verkuil escreveu:
>
>> On 09/28/2017 12:23 AM, Mauro Carvalho Chehab wrote:
>>> Add a glossary of terms for V4L2, as several concepts are complex
>>> enough to cause
Em Tue, 10 Oct 2017 09:47:13 +0200
Hans Verkuil escreveu:
> On 09/28/2017 12:23 AM, Mauro Carvalho Chehab wrote:
> > Add a glossary of terms for V4L2, as several concepts are complex
> > enough to cause misunderstandings.
> >
> > Signed-off-by: Mauro Carvalho Chehab
On 09/28/2017 12:23 AM, Mauro Carvalho Chehab wrote:
> Add a glossary of terms for V4L2, as several concepts are complex
> enough to cause misunderstandings.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/media/uapi/v4l/glossary.rst | 136
>
Hi Mauro,
On Fri, Oct 06, 2017 at 01:22:29PM +0300, Sakari Ailus wrote:
> > +V4L2 device node
> > + A device node that is associated to a V4L2 main driver,
> > + as specified in :ref:`v4l2_device_naming`.
I think we need to name the interface, not so much their instances.
How about
Hi Mauro,
Thanks for continuing the work on this!
On Wed, Sep 27, 2017 at 07:23:43PM -0300, Mauro Carvalho Chehab wrote:
> Add a glossary of terms for V4L2, as several concepts are complex
> enough to cause misunderstandings.
>
> Signed-off-by: Mauro Carvalho Chehab
>
Add a glossary of terms for V4L2, as several concepts are complex
enough to cause misunderstandings.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/v4l/glossary.rst | 136 ++
Documentation/media/uapi/v4l/v4l2.rst | 1
15 matches
Mail list logo