On 10/04/2018 05:03 PM, Mauro Carvalho Chehab wrote:
> From: Mauro Carvalho Chehab
>
> Add a glossary of terms used within the media userspace API
> documentation, as several concepts are complex enough to cause
> misunderstandings.
>
> Signed-off-by: Mauro Carvalho Chehab
With the understandi
From: Mauro Carvalho Chehab
Add a glossary of terms used within the media userspace API
documentation, as several concepts are complex enough to cause
misunderstandings.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/media_uapi.rst| 3 +
Documentation/media/uapi/glossary.rs
Em Thu, 4 Oct 2018 10:27:06 -0300
Mauro Carvalho Chehab escreveu:
> > > + For V4L2 hardware, this is also known as V4L2 main driver.
> >
> > Do we use the term V4L2 main driver in the V4L2 spec ?
>
> Right now, I don't think we use, but this is somethin
on't think the definition is correct. Bridges, as defined in
> V4L2, are opposed to subdevs, while "media hardware" in your definition
> includes everything. This needs to be clarified.
Please notice that the goal of this glossary is to be generic, and not
specific to V4L2. Extra care shou
ssed this
previously, but if we want to write a glossary, it should be in English. Maybe
we need to involve a native English speaker here. Kieran ? :-)
Additionally, I don't think the definition is correct. Bridges, as defined in
V4L2, are opposed to subdevs, while "media hardware&q
Em Thu, 4 Oct 2018 13:11:12 +0200
Hans Verkuil escreveu:
> On 10/04/18 12:58, Mauro Carvalho Chehab wrote:
> > From: Mauro Carvalho Chehab
> >
> > Add a glossary of terms used within the media userspace API
> > documentation, as several concepts are complex enough to cause
> > misunderstandings
On 10/04/18 12:58, Mauro Carvalho Chehab wrote:
> From: Mauro Carvalho Chehab
>
> Add a glossary of terms used within the media userspace API
> documentation, as several concepts are complex enough to cause
> misunderstandings.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/med
From: Mauro Carvalho Chehab
Add a glossary of terms used within the media userspace API
documentation, as several concepts are complex enough to cause
misunderstandings.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/media_uapi.rst| 3 +
Documentation/media/uapi/glossary.rs
Em Mon, 1 Oct 2018 17:20:26 +0200
Hans Verkuil escreveu:
> On 09/25/2018 09:14 PM, Mauro Carvalho Chehab wrote:
> > From: Mauro Carvalho Chehab
> >
> > Add a glossary of terms used within the media userspace API
> > documentation, as several concepts are complex enough to cause
> > misunderstan
On 09/25/2018 09:14 PM, Mauro Carvalho Chehab wrote:
> From: Mauro Carvalho Chehab
>
> Add a glossary of terms used within the media userspace API
> documentation, as several concepts are complex enough to cause
> misunderstandings.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
>
> v3:
> -
From: Mauro Carvalho Chehab
Add a glossary of terms used within the media userspace API
documentation, as several concepts are complex enough to cause
misunderstandings.
Signed-off-by: Mauro Carvalho Chehab
---
v3:
- Add SPDX header and dual-license the glossary
- Make glossary generic eno
From: 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
---
v2.: Did some changes based on Sakari's feedback.
Documentation/media/media_uapi.rst| 2 +
Documentation/media/u
Em Tue, 25 Sep 2018 16:03:57 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> Thanks for the set! A few quick comments below, mainly additions and language.
>
> On Tue, Sep 25, 2018 at 09:06:51AM -0300, Mauro Carvalho Chehab wrote:
> > From: Mauro Carvalho Chehab
> >
> > Add a glossary of terms f
Hi Mauro,
Thanks for the set! A few quick comments below, mainly additions and language.
On Tue, Sep 25, 2018 at 09:06:51AM -0300, Mauro Carvalho Chehab wrote:
> From: Mauro Carvalho Chehab
>
> Add a glossary of terms for V4L2, as several concepts are complex
> enough to cause misunderstandings
From: 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 | 108 ++
Documentation/media/uapi/v4l/v4l2.rst | 1 +
2
instance, it mentions that radio devices don't support video streaming
> related IOCTLs.
FYI, when this chapter was written, radio devices did support video
streaming ioctls :-)
As I explained on a previous email, Only several years after V4L2
spec was written, it was decided to nack using
#x27;d be much easier to maintain
> > consistency in naming and definitions if V4L2 sub-device nodes were also
> > documented to be V4L2 device nodes, just as any other device nodes exposed
> > by drivers through the V4L2 framework.
> >
> > >
> > > The definiti
More (mostly) small stuff:
On 10/10/2017 01:45 PM, 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 | 167
> ++
should let it clear that only the devnodes
> > implemented by the V4L2 main driver are considered as
> > V4L2 device nodes.
>
> Why? I don't think we should make assumptions on which driver exposes a
> device node; this is not visible to the user space after all.
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 node that is associated
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 | 167 ++
Documentation/media/uapi/v4l/v4l2.rst | 1 +
2 files changed, 168 in
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 :ref:`v4l2_device_naming`.
>
> I think we
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 devices, for
> > instance. Ho
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 | 150 ++
Documentation/media/uapi/v4l/v4l2.rst | 1 +
2 files changed, 151 in
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 cause misunderstandings
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 implements support for a
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 another device (or
> tr
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 misunderstandings.
>>>
>>> Signed-
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
> > ---
> > Documentation/m
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
> ++
> Docu
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 addin
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
> ---
> Documentation/media
Hi Mauro,
On Thu, Oct 05, 2017 at 09:26:51AM -0300, Mauro Carvalho Chehab wrote:
> > > > > +
> > > > > + See :ref:`media_controller`.
> > > > > +
> > > > > +MC-centric
> > > > > + V4L2 hardware that requires a Media controller.
> > > > > +
> > > > > + See :ref:`v4l2_hardware_contro
On Thu, Oct 05, 2017 at 03:39:29PM -0300, Mauro Carvalho Chehab wrote:
> Em Thu, 5 Oct 2017 11:21:07 +0300
> Sakari Ailus escreveu:
>
> > Hi Mauro,
> >
> > My apologies for the late reply.
> >
> > On Tue, Aug 29, 2017 at 10:07:50AM -0300, Mauro Carvalho Chehab wrote:
> > > Em Tue, 29 Aug 2017 1
Em Thu, 5 Oct 2017 11:21:07 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> My apologies for the late reply.
>
> On Tue, Aug 29, 2017 at 10:07:50AM -0300, Mauro Carvalho Chehab wrote:
> > Em Tue, 29 Aug 2017 10:47:48 +0300
> > Sakari Ailus escreveu:
> >
> > > Hi Mauro,
> > >
> > > Thanks for
Em Thu, 5 Oct 2017 11:21:07 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> My apologies for the late reply.
>
> On Tue, Aug 29, 2017 at 10:07:50AM -0300, Mauro Carvalho Chehab wrote:
> > Em Tue, 29 Aug 2017 10:47:48 +0300
> > Sakari Ailus escreveu:
> >
> > > Hi Mauro,
> > >
> > > Thanks for
Hi Mauro,
My apologies for the late reply.
On Tue, Aug 29, 2017 at 10:07:50AM -0300, Mauro Carvalho Chehab wrote:
> Em Tue, 29 Aug 2017 10:47:48 +0300
> Sakari Ailus escreveu:
>
> > Hi Mauro,
> >
> > Thanks for the update. A few comments below.
> >
> > On Mon, Aug 28, 2017 at 09:53:55AM -0300
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 +
2 files changed, 137 in
Em Fri, 1 Sep 2017 12:26:39 +0200
Hans Verkuil escreveu:
> On 29/08/17 15:17, 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/u
On 29/08/17 15:17, 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 | 150
> ++
> Documenta
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 | 150 ++
Documentation/media/uapi/v4l/v4l2.rst | 1 +
2 files changed, 151 in
Em Tue, 29 Aug 2017 10:47:48 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> Thanks for the update. A few comments below.
>
> On Mon, Aug 28, 2017 at 09:53:55AM -0300, Mauro Carvalho Chehab wrote:
> > Add a glossary of terms for V4L2, as several concepts are complex
> > enough to cause misundersta
Hi Mauro,
Thanks for the update. A few comments below.
On Mon, Aug 28, 2017 at 09:53:55AM -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
> ---
> Documentation/
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 | 147 ++
Documentation/media/uapi/v4l/v4l2.rst | 1 +
2 files changed, 148 in
This is a partial review. I think I need to review the other patches first
before continuing this review. But it doesn't hurt to post this now.
On 26/08/17 13:53, Mauro Carvalho Chehab wrote:
> Add a glossary of terms for V4L2, as several concepts are complex
> enough to cause misunderstandings.
>
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 | 98 +++
Documentation/media/uapi/v4l/v4l2.rst | 1 +
2 files changed, 99 inse
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 | 95 +++
Documentation/media/uapi/v4l/v4l2.rst | 1 +
2 files changed, 96 inse
Am 21.01.2013 22:39, schrieb Hans Verkuil:
> On Mon January 21 2013 22:25:37 Frank Schäfer wrote:
>> Hi Hans,
>>
>> Am 21.01.2013 09:59, schrieb Hans Verkuil:
>>> On Sun January 20 2013 22:15:51 Frank Schäfer wrote:
Hi Hans,
I noticed that there's code in the v4l2 core that enables/d
On Mon January 21 2013 22:25:37 Frank Schäfer wrote:
> Hi Hans,
>
> Am 21.01.2013 09:59, schrieb Hans Verkuil:
> > On Sun January 20 2013 22:15:51 Frank Schäfer wrote:
> >> Hi Hans,
> >>
> >> I noticed that there's code in the v4l2 core that enables/disables
> >> ioctls and checks some of the para
Hi Hans,
Am 21.01.2013 09:59, schrieb Hans Verkuil:
> On Sun January 20 2013 22:15:51 Frank Schäfer wrote:
>> Hi Hans,
>>
>> I noticed that there's code in the v4l2 core that enables/disables
>> ioctls and checks some of the parameters depending on the device type.
>> While reading the code an com
On Sun January 20 2013 22:15:51 Frank Schäfer wrote:
> Hi Hans,
>
> I noticed that there's code in the v4l2 core that enables/disables
> ioctls and checks some of the parameters depending on the device type.
> While reading the code an comparing it to the V4L2 API document, some
> more questions c
Hi Hans,
I noticed that there's code in the v4l2 core that enables/disables
ioctls and checks some of the parameters depending on the device type.
While reading the code an comparing it to the V4L2 API document, some
more questions came up:
1) Video devices with VBI functionality:
The spec says:
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/biblio.xml | 40 +++
Documentation/DocBook/media/v4l/controls.xml | 161 ++
Documentation/DocBook/media/v4l/v4l2.xml |1 +
3 files changed, 202 insertions(+)
diff --git a/Documentation/DocBoo
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/controls.xml | 149 +++
Documentation/DocBook/media/v4l/v4l2.xml |1 +
.../DocBook/media/v4l/vidioc-subdev-g-edid.xml | 152
3 files changed, 302 insertions(+)
create mo
From: Hans Verkuil
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/compat.xml | 12 ++
Documentation/DocBook/media/v4l/v4l2.xml |6 +
.../DocBook/media/v4l/vidioc-enum-freq-bands.xml | 179
.../DocBook/media/v4l/vidioc-g-frequency.
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/controls.xml | 149 +++
Documentation/DocBook/media/v4l/v4l2.xml |1 +
.../DocBook/media/v4l/vidioc-subdev-g-edid.xml | 152
3 files changed, 302 insertions(+)
create mo
From: Hans Verkuil
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/compat.xml | 12 ++
Documentation/DocBook/media/v4l/v4l2.xml |6 +
.../DocBook/media/v4l/vidioc-enum-freq-bands.xml | 179
.../DocBook/media/v4l/vidioc-g-frequency.
From: Hans Verkuil
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/compat.xml | 12 ++
Documentation/DocBook/media/v4l/v4l2.xml |6 +
.../DocBook/media/v4l/vidioc-enum-freq-bands.xml | 152
.../DocBook/media/v4l/vidioc-g-frequency.
Thanks for the patch, Hans
On Wed, 6 Jun 2012, Hans Verkuil wrote:
> Two small docbook fixes:
>
> - prepare-buf was not positioned in alphabetical order, moved to the right
> place.
> - the format field in create_bufs had the wrong type in the documentation
>
> Regards,
>
> Hans
>
> Si
Two small docbook fixes:
- prepare-buf was not positioned in alphabetical order, moved to the right
place.
- the format field in create_bufs had the wrong type in the documentation
Regards,
Hans
Signed-off-by: Hans Verkuil
diff --git a/Documentation/DocBook/media/v4l/v4l2.xml
b/Docu
From: Hans Verkuil
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/controls.xml | 149 +++
Documentation/DocBook/media/v4l/v4l2.xml |1 +
.../DocBook/media/v4l/vidioc-subdev-g-edid.xml | 152
3 files changed, 302 ins
From: Hans Verkuil
Based in part on an earlier patch from .
Signed-off-by: Hans Verkuil
---
.../DocBook/media/v4l/vidioc-g-modulator.xml | 38 +---
Documentation/DocBook/media/v4l/vidioc-g-tuner.xml | 97 +---
.../DocBook/media/v4l/vidioc-s-hw-freq-seek.xml|
From: Hans Verkuil
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/common.xml | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/Documentation/DocBook/media/v4l/common.xml
b/Documentation/DocBook/media/v4l/common.xml
index 4101aeb..b91d253
From: Hans Verkuil
Update the spec with the new capabilities and specify new error codes for
S_HW_FREQ_SEEK.
Signed-off-by: Hans Verkuil
Acked-by: Hans de Goede
---
.../DocBook/media/v4l/vidioc-g-frequency.xml |6 ++
Documentation/DocBook/media/v4l/vidioc-g-tuner.xml | 12
Hi,
Comments inline.
On 05/27/2012 01:50 PM, Hans Verkuil wrote:
From: Hans Verkuil
Based in part on an earlier patch from.
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/common.xml | 28 --
.../DocBook/media/v4l/vidioc-g-modulator.xml | 38 +---
Small typo, see comment inline, with that fixed:
Acked-by: Hans de Goede
On 05/27/2012 01:50 PM, Hans Verkuil wrote:
From: Hans Verkuil
Update the spec with the new capabilities and specify new error codes for
S_HW_FREQ_SEEK.
Signed-off-by: Hans Verkuil
---
.../DocBook/media/v4l/vidioc-g-f
From: Hans Verkuil
Update the spec with the new capabilities and specify new error codes for
S_HW_FREQ_SEEK.
Signed-off-by: Hans Verkuil
---
.../DocBook/media/v4l/vidioc-g-frequency.xml |6 ++
Documentation/DocBook/media/v4l/vidioc-g-tuner.xml | 12
.../DocBook
From: Hans Verkuil
Based in part on an earlier patch from .
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/common.xml | 28 --
.../DocBook/media/v4l/vidioc-g-modulator.xml | 38 +---
Documentation/DocBook/media/v4l/vidioc-g-tuner.xml | 97 ++
From: Hans Verkuil
Signed-off-by: Hans Verkuil
Reviewed-by: Mauro Carvalho Chehab
---
Documentation/DocBook/media/v4l/biblio.xml | 18 ++
Documentation/DocBook/media/v4l/common.xml | 32 +--
Documentation/DocBook/media/v4l/compat.xml | 13 ++
Documentation/DocBook
Signed-off-by: Hans Verkuil
Reviewed-by: Mauro Carvalho Chehab
---
Documentation/DocBook/media/v4l/v4l2.xml |3 +
.../DocBook/media/v4l/vidioc-g-dv-timings.xml | 121 ++--
2 files changed, 116 insertions(+), 8 deletions(-)
diff --git a/Documentation/DocBook/m
On Tuesday, February 28, 2012 12:01:01 Mauro Carvalho Chehab wrote:
> Em 03-02-2012 08:06, Hans Verkuil escreveu:
> > From: Hans Verkuil
>
> The comments for patch 1 apply here. So, I won't repeat myself ;) There's
> just one
> minor comment below.
>
> > +
>
> Don't insert editor-specific para
Em 03-02-2012 08:06, Hans Verkuil escreveu:
> From: Hans Verkuil
The comments for patch 1 apply here. So, I won't repeat myself ;) There's just
one
minor comment below.
>
> Signed-off-by: Hans Verkuil
> ---
> Documentation/DocBook/media/v4l/v4l2.xml |3 +
> .../DocBook/media/v4
From: Hans Verkuil
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/v4l2.xml |3 +
.../DocBook/media/v4l/vidioc-dv-timings-cap.xml| 205
.../DocBook/media/v4l/vidioc-enum-dv-timings.xml | 113 +++
.../DocBook/media/v4l/vidioc-g-d
> On Monday 16 January 2012 23:16:31 Guennadi Liakhovetski wrote:
> > >>> On Mon, 16 Jan 2012, Mauro Carvalho Chehab wrote:
> > >>>> This is an automatic generated email to let you know that the
> > >>>> following patch were queued at the
> > &g
On Mon, 16 Jan 2012, Mauro Carvalho Chehab wrote:
> >>>> This is an automatic generated email to let you know that the following
> >>>> patch were queued at the http://git.linuxtv.org/media_tree.git tree:
> >>>>
> >>>> Subject: [media] V4L2
ic generated email to let you know that the following
>>>> patch were queued at the http://git.linuxtv.org/media_tree.git tree:
>>>>
>>>> Subject: [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation
>>>> Author: Hans Verkuil
>>>>
tch were queued at the http://git.linuxtv.org/media_tree.git tree:
> > >
> > > Subject: [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation
> > > Author: Hans Verkuil
> > > Date:Wed Jan 11 07:37:54 2012 -0300
> >
> > [snip]
> >
> > &
On Monday 16 January 2012 23:16:31 Guennadi Liakhovetski wrote:
> On Mon, 16 Jan 2012, Mauro Carvalho Chehab wrote:
> > This is an automatic generated email to let you know that the following
> > patch were queued at the http://git.linuxtv.org/media_tree.git tree:
> >
>
On Mon, 16 Jan 2012, Mauro Carvalho Chehab wrote:
> This is an automatic generated email to let you know that the following patch
> were queued at the
> http://git.linuxtv.org/media_tree.git tree:
>
> Subject: [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation
owing changes since commit 240ab508aa9fb7a294b0ecb563b19ead000b2463:
[media] [PATCH] don't reset the delivery system on DTV_CLEAR (2012-01-10
23:44:07 -0200)
are available in the git repository at:
git://linuxtv.org/hverkuil/media_tree.git spec3
Hans Verkuil (5):
v4l2 spec: clarif
From: Hans Verkuil
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/vidioc-g-fbuf.xml | 23
1 files changed, 14 insertions(+), 9 deletions(-)
diff --git a/Documentation/DocBook/media/v4l/vidioc-g-fbuf.xml
b/Documentation/DocBook/media/v4l/vidioc-g-fbuf.xm
From: Hans Verkuil
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/vidioc-dqevent.xml | 17 +++-
.../DocBook/media/v4l/vidioc-subscribe-event.xml | 142 +++-
2 files changed, 157 insertions(+), 2 deletions(-)
diff --git a/Documentation/DocBook/media/v4l/vid
From: Hans Verkuil
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media-entities.tmpl |1 +
Documentation/DocBook/v4l/vidioc-dqevent.xml | 17 +++-
.../DocBook/v4l/vidioc-subscribe-event.xml | 142 +++-
3 files changed, 158 insertions(+), 2 d
On Saturday, January 01, 2011 22:25:04 Devin Heitmueller wrote:
> Hi Hans,
>
> Thanks for the feedback.
>
> On Sat, Jan 1, 2011 at 4:18 PM, Hans Verkuil wrote:
> >> This basically means that a video tuner will bail out, which sounds
> >> good because the rest of the function supposedly assumes a
Hi Hans,
Thanks for the feedback.
On Sat, Jan 1, 2011 at 4:18 PM, Hans Verkuil wrote:
>> This basically means that a video tuner will bail out, which sounds
>> good because the rest of the function supposedly assumes a radio
>> device. However, as a result the has_signal() call (which returns
>
On Saturday, January 01, 2011 21:52:35 Devin Heitmueller wrote:
> I have been doing some application conformance for VLC, and I noticed
> something interesting with regards to the G_TUNER call.
>
> If you have a tuner which supports sleeping, making a G_TUNER call
> essentially returns garbage.
>
I have been doing some application conformance for VLC, and I noticed
something interesting with regards to the G_TUNER call.
If you have a tuner which supports sleeping, making a G_TUNER call
essentially returns garbage.
===
r...@devin-laptop2:~# v4l2-ctl -d /dev/video1 --get-tuner
Tuner:
Nam
Hi, Kamil
> Hello,
>
> > From: Jonghun Han [mailto:jonghun@samsung.com]
> > Sent: 06 December 2010 07:57
> >
> > Hi,
> >
> > If MFC(encoder/decoder) has a single node,
> > how to know application's object before VIDIOC_S_FMT calling ?
>
> You're right. No way to know that before.
>
> > VID
Hello,
> From: Jonghun Han [mailto:jonghun@samsung.com]
> Sent: 06 December 2010 07:57
>
> Hi,
>
> If MFC(encoder/decoder) has a single node,
> how to know application's object before VIDIOC_S_FMT calling ?
You're right. No way to know that before.
> VIDIOC_S_CTRL can be called before VIDI
n Han; Laurent Pinchart; jaeryul...@samsung.com;
linux-
> me...@vger.kernel.org
> Subject: Re: RFC: Problem of using v4l2 spec with codec function
>
> Hi all,
> I would side with Laurent on this. Judging by formats seems to be
> enough for this driver and it has great, in my opinion
Hi all,
I would side with Laurent on this. Judging by formats seems to be
enough for this driver and it has great, in my opinion, advantages of
a) not overcomplicating things for applications b) not adding new
pieces to the API...
--
Best regards,
Pawel Osciak
--
To unsubscribe from this list: se
Hi,
Hans Verkuil [hverk...@xs4all.nl] wrote:
> >
> > In two nodes case, application cannot know the feature via
> > VIDIOC_QUERYCAP.
> > Because decoder and encoder return the same CAPABILITY. OUTPUT and
> CAPTURE
> > So application should call VIDIOC_G_FMT to recognize the feature.
>
> The curr
9:17 PM
> To: Jonghun Han
> Cc: 'Laurent Pinchart'; jaeryul...@samsung.com;
linux-media@vger.kernel.org
> Subject: RE: RFC: Problem of using v4l2 spec with codec function
>
>
> >
> > Hi,
> >
> > In two nodes case, application cannot know the fea
Hi Hans,
On Monday 29 November 2010 11:36:03 Hans Verkuil wrote:
> > On Monday 29 November 2010 08:34:06 Hans Verkuil wrote:
[snip]
> >> I *think* that what you are saying is that your hardware can have just a
> >> single 'm2m' video instance and so you want to allow the user to switch
> >> betw
27;Hans Verkuil'
>> Cc: jaeryul...@samsung.com; linux-media@vger.kernel.org
>> Subject: RE: RFC: Problem of using v4l2 spec with codec function
>>
>>
>> Laurent Pinchart wrote:
>>
>> > -Original Message-
>> > From: linux-media-ow...
dia-ow...@vger.kernel.org [mailto:linux-media-
> ow...@vger.kernel.org] On Behalf Of Jonghun Han
> Sent: Monday, November 29, 2010 8:49 PM
> To: 'Laurent Pinchart'; 'Hans Verkuil'
> Cc: jaeryul...@samsung.com; linux-media@vger.kernel.org
> Subject: RE: RFC: Problem of using v4l2
ia@vger.kernel.org
> Subject: Re: RFC: Problem of using v4l2 spec with codec function
>
> Hi,
>
> > If so, then I think creating a so-called 'private' control for your
> > hardware would be the best way to go. As an example of private controls
> > search for th
> Hi,
>
> On Monday 29 November 2010 08:34:06 Hans Verkuil wrote:
>> On Monday, November 29, 2010 00:52:15 Jaeryul Oh wrote:
>> > Hello, everyone.
>> >
>> > When it comes to using v4l2 standard spec, I have a question about
>> that.
>> >
>> > A month ago, Kamil Debski posted second version for the
Hi,
On Monday 29 November 2010 08:34:06 Hans Verkuil wrote:
> On Monday, November 29, 2010 00:52:15 Jaeryul Oh wrote:
> > Hello, everyone.
> >
> > When it comes to using v4l2 standard spec, I have a question about that.
> >
> > A month ago, Kamil Debski posted second version for the driver of a
On Monday, November 29, 2010 00:52:15 Jaeryul Oh wrote:
> Hello, everyone.
>
> When it comes to using v4l2 standard spec, I have a question about that.
>
> A month ago, Kamil Debski posted second version for the driver of a hw video
> codec.
> To be exact, it is decoding function of hw video cod
1 - 100 of 153 matches
Mail list logo
