Re: [PATCH v5] media: docs: add glossary.rst with common terms used at V4L2 spec

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

[PATCH v5] media: docs: add glossary.rst with common terms used at V4L2 spec

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 +

Re: [PATCH v3] media: docs: add glossary.rst with common terms used at V4L2 spec

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 something tha

Re: [PATCH v3] media: docs: add glossary.rst with common terms used at V4L2 spec

, 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 should be taken if we want to talk about "su

Re: [PATCH v3] media: docs: add glossary.rst with common terms used at V4L2 spec

y, 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" in your definiti

Re: [PATCH v4] media: docs: add glossary.rst with common terms used at V4L2 spec

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 > >

Re: [PATCH v4] media: docs: add glossary.rst with common terms used at V4L2 spec

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 > --- >

[PATCH v4] media: docs: add glossary.rst with common terms used at V4L2 spec

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 +

Re: [PATCH v3] media: docs: add glossary.rst with common terms used at V4L2 spec

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 > >

Re: [PATCH v3] media: docs: add glossary.rst with common terms used at V4L2 spec

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: > -

[PATCH v3] media: docs: add glossary.rst with common terms used at V4L2 spec

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

[PATCH v2] media: docs: add glossary.rst with common terms used at V4L2 spec

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 +

Re: [PATCH 1/3] media: add glossary.rst with common terms used at V4L2 spec

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

Re: [PATCH 1/3] media: add glossary.rst with common terms used at V4L2 spec

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

[PATCH 1/3] media: add glossary.rst with common terms used at V4L2 spec

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 +

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

. For > 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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

> > Hmm. There seems to be a gap here. It'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

Re: [PATCH v8 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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 > --- >

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

framework. > > > > > The definition 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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

[PATCH v8 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

[PATCH] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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 >

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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 >

Re: [PATCH v5 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v5 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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: > > >

Re: [PATCH v5 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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: > >

Re: [PATCH v5 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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: > >

Re: [PATCH v5 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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,

[PATCH v7 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v6 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v6 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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 >

[PATCH v6 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v5 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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 > >

Re: [PATCH v5 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

[PATCH v5 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: [PATCH v4 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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.

[PATCH v4 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

[PATCH v3 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec

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

Re: V4L2 spec / core questions

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 came

V4L2 spec / core questions

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:

[RFCv3 PATCH 2/8] V4L2 spec: document the new DV controls and ioctls.

Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- 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

[RFCv2 PATCH 2/7] V4L2 spec: document the new DV controls and ioctls.

Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- 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

[PATCH 1/5] v4l2 spec: add VIDIOC_ENUM_FREQ_BANDS documentation.

From: Hans Verkuil hans.verk...@cisco.com Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- Documentation/DocBook/media/v4l/compat.xml | 12 ++ Documentation/DocBook/media/v4l/v4l2.xml |6 + .../DocBook/media/v4l/vidioc-enum-freq-bands.xml | 179

[PATCH 3/6] v4l2 spec: add VIDIOC_ENUM_FREQ_BANDS documentation.

From: Hans Verkuil hans.verk...@cisco.com Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- Documentation/DocBook/media/v4l/compat.xml | 12 ++ Documentation/DocBook/media/v4l/v4l2.xml |6 + .../DocBook/media/v4l/vidioc-enum-freq-bands.xml | 179

[RFCv1 PATCH 2/7] V4L2 spec: document the new DV controls and ioctls.

Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- 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

[RFC PATCH 3/6] v4l2 spec: add VIDIOC_ENUM_FREQ_BANDS documentation.

From: Hans Verkuil hans.verk...@cisco.com Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- Documentation/DocBook/media/v4l/compat.xml | 12 ++ Documentation/DocBook/media/v4l/v4l2.xml |6 + .../DocBook/media/v4l/vidioc-enum-freq-bands.xml | 152

Re: [PATCH for v3.5] V4L2 spec fix

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

[PATCH for v3.5] V4L2 spec fix

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 hans.verk...@cisco.com diff --git

[RFCv2 PATCH 2/6] v4l2 spec: document the new v4l2_tuner capabilities

From: Hans Verkuil hans.verk...@cisco.com Update the spec with the new capabilities and specify new error codes for S_HW_FREQ_SEEK. Signed-off-by: Hans Verkuil hans.verk...@cisco.com Acked-by: Hans de Goede hdego...@redhat.com --- .../DocBook/media/v4l/vidioc-g-frequency.xml |6

[RFCv2 PATCH 6/6] V4L2 spec: clarify a few modulator issues.

From: Hans Verkuil hans.verk...@cisco.com Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- Documentation/DocBook/media/v4l/common.xml | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/Documentation/DocBook/media/v4l/common.xml

[RFCv1 PATCH 5/5] V4L2 spec: add frequency band documentation.

From: Hans Verkuil hans.verk...@cisco.com Based in part on an earlier patch from hallima...@gmail.com. Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- Documentation/DocBook/media/v4l/common.xml | 28 -- .../DocBook/media/v4l/vidioc-g-modulator.xml | 38 +---

[RFCv1 PATCH 2/5] v4l2 spec: document the new v4l2_tuner capabilities

From: Hans Verkuil hans.verk...@cisco.com Update the spec with the new capabilities and specify new error codes for S_HW_FREQ_SEEK. Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- .../DocBook/media/v4l/vidioc-g-frequency.xml |6 ++

Re: [RFCv1 PATCH 2/5] v4l2 spec: document the new v4l2_tuner capabilities

Small typo, see comment inline, with that fixed: Acked-by: Hans de Goede hdego...@redhat.com On 05/27/2012 01:50 PM, Hans Verkuil wrote: From: Hans Verkuilhans.verk...@cisco.com Update the spec with the new capabilities and specify new error codes for S_HW_FREQ_SEEK. Signed-off-by: Hans

Re: [RFCv1 PATCH 5/5] V4L2 spec: add frequency band documentation.

Hi, Comments inline. On 05/27/2012 01:50 PM, Hans Verkuil wrote: From: Hans Verkuilhans.verk...@cisco.com Based in part on an earlier patch fromhallima...@gmail.com. Signed-off-by: Hans Verkuilhans.verk...@cisco.com --- Documentation/DocBook/media/v4l/common.xml | 28 --

[PATCH 4/7] V4L2 spec: document the new V4L2 DV timings ioctls.

From: Hans Verkuil hans.verk...@cisco.com Signed-off-by: Hans Verkuil hans.verk...@cisco.com Reviewed-by: Mauro Carvalho Chehab mche...@redhat.com --- Documentation/DocBook/media/v4l/biblio.xml | 18 ++ Documentation/DocBook/media/v4l/common.xml | 32 +--

[RFCv3 PATCH 4/6] V4L2 spec: document the new V4L2 DV timings ioctls.

Signed-off-by: Hans Verkuil hans.verk...@cisco.com Reviewed-by: Mauro Carvalho Chehab mche...@redhat.com --- Documentation/DocBook/media/v4l/v4l2.xml |3 + .../DocBook/media/v4l/vidioc-g-dv-timings.xml | 121 ++-- 2 files changed, 116 insertions(+), 8

Re: [RFCv1 PATCH 4/6] V4L2 spec: document the new V4L2 DV timings ioctls.

Em 03-02-2012 08:06, Hans Verkuil escreveu: From: Hans Verkuil hans.verk...@cisco.com 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 hans.verk...@cisco.com --- Documentation/DocBook/media/v4l/v4l2.xml

Re: [RFCv1 PATCH 4/6] V4L2 spec: document the new V4L2 DV timings ioctls.

On Tuesday, February 28, 2012 12:01:01 Mauro Carvalho Chehab wrote: Em 03-02-2012 08:06, Hans Verkuil escreveu: From: Hans Verkuil hans.verk...@cisco.com The comments for patch 1 apply here. So, I won't repeat myself ;) There's just one minor comment below. +!-- +Local Variables:

[RFCv1 PATCH 4/6] V4L2 spec: document the new V4L2 DV timings ioctls.

From: Hans Verkuil hans.verk...@cisco.com Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- 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

Re: [git:v4l-dvb/for_v3.3] [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation

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: Subject: [media] V4L2 Spec

Re: [git:v4l-dvb/for_v3.3] [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation

/media_tree.git tree: Subject: [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation Author: Hans Verkuil hans.verk...@cisco.com Date:Wed Jan 11 07:37:54 2012 -0300 [snip] diff --git a/Documentation/DocBook/media/v4l/vidioc-g-output.xml b/Documentation/DocBook

Re: [git:v4l-dvb/for_v3.3] [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation

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 hans.verk...@cisco.com Date:Wed Jan 11 07:37:54 2012 -0300 [snip] diff --git a/Documentation/DocBook/media/v4l/vidioc-g

Re: [git:v4l-dvb/for_v3.3] [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation

: 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 Author: Hans Verkuil hans.verk...@cisco.com Date:Wed Jan 11 07:37:54 2012 -0300

Re: [git:v4l-dvb/for_v3.3] [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation

: 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 Author: Hans

Re: [git:v4l-dvb/for_v3.3] [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation

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 Author: Hans Verkuil

[GIT PULL FOR v3.3] V4L2 Spec updates

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: clarify usage

[RFCv2 PATCH 1/3] v4l2 spec: clarify usage of V4L2_FBUF_FLAG_OVERLAY

From: Hans Verkuil hans.verk...@cisco.com Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- 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

[RFCv3 PATCH 15/18] V4L2 spec: document control events.

From: Hans Verkuil hans.verk...@cisco.com Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- Documentation/DocBook/media/v4l/vidioc-dqevent.xml | 17 +++- .../DocBook/media/v4l/vidioc-subscribe-event.xml | 142 +++- 2 files changed, 157 insertions(+), 2 deletions(-)

[RFCv2 PATCH 10/11] V4L2 spec: document control events.

From: Hans Verkuil hans.verk...@cisco.com Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- Documentation/DocBook/media-entities.tmpl |1 + Documentation/DocBook/v4l/vidioc-dqevent.xml | 17 +++- .../DocBook/v4l/vidioc-subscribe-event.xml | 142

V4L2 spec behavior for G_TUNER and T_STANDBY

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:

Re: V4L2 spec behavior for G_TUNER and T_STANDBY

Hi Hans, Thanks for the feedback. On Sat, Jan 1, 2011 at 4:18 PM, Hans Verkuil hverk...@xs4all.nl 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

Re: V4L2 spec behavior for G_TUNER and T_STANDBY

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 hverk...@xs4all.nl wrote: This basically means that a video tuner will bail out, which sounds good because the rest of the function supposedly

RE: RFC: Problem of using v4l2 spec with codec function

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

RE: RFC: Problem of using v4l2 spec with codec function

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. VIDIOC_S_CTRL can be

RE: RFC: Problem of using v4l2 spec with codec function

...@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, advantages of a) not overcomplicating things

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, 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:

RE: RFC: Problem of using v4l2 spec with codec function

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 current V4L API

Re: RFC: Problem of using v4l2 spec with codec function

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 hw video

Re: RFC: Problem of using v4l2 spec with codec function

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 hw

RE: RFC: Problem of using v4l2 spec with codec function

: RFC: Problem of using v4l2 spec with codec function Hi, snip 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 the V4L2_CID_MPEG_CX2341X_BASE define in videodev2.h. I would rely

RE: RFC: Problem of using v4l2 spec with codec function

[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 spec with codec function Laurent Pinchart

RE: RFC: Problem of using v4l2 spec with codec function

: Problem of using v4l2 spec with codec function Laurent Pinchart wrote: -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media- ow...@vger.kernel.org] On Behalf Of Laurent Pinchart Sent: Monday, November 29, 2010 6:20 PM To: Hans Verkuil Cc: jaeryul

Re: RFC: Problem of using v4l2 spec with codec function

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 between the

RE: RFC: Problem of using v4l2 spec with codec function

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 feature via VIDIOC_QUERYCAP. Because decoder and encoder return the same

RFC: Problem of using v4l2 spec with codec function

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 codec which is called MFC(Multi Format Codec). For members not

Re: RFC: Problem of using v4l2 spec with codec function

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 codec

Re: problem building v4l2-spec from docbook source

Em Wed, 09 Sep 2009 00:07:05 -0400 CityK ci...@rogers.com escreveu: We've got too many entry points/links to things -- which lends itself to becoming a maintenance nightmare (not blaming anyone, just pointing out the obvious). For example: although the updated info was applied here:

Re: problem building v4l2-spec from docbook source

dvb and v4l spec in pdf? For dvb the v3 is still on the documentation page. The pdf version of V4L2 spec is currently broken: several tables and graphics don't fit at the page size. If you (or someone else) is interested on fixing it, I'll add a pointer at linuxtv.org for the updated

Re: problem building v4l2-spec from docbook source

the v3 is still on the documentation page. The pdf version of V4L2 spec is currently broken: several tables and graphics don't fit at the page size. If you (or someone else) is interested on fixing it, I'll add a pointer at linuxtv.org for the updated version, and improve the script to auto

Re: problem building v4l2-spec from docbook source

Em Sat, 05 Sep 2009 18:54:27 +0100 Peter Brouwer pb.mailli...@googlemail.com escreveu: Is it possible to create a link on the linuxtv.org website to the latest dvb and v4l spec in pdf? For dvb the v3 is still on the documentation page. The pdf version of V4L2 spec is currently broken

Re: problem building v4l2-spec from docbook source

=boldMiscelaneous keys/emphasis/entry/row +rowentryemphasis role=boldMiscelaneous keys/emphasis/entry/row changeset: 12615:2b49813f8482 tag: tip user:Mauro Carvalho Chehab mche...@redhat.com date:Thu Sep 03 09:06:34 2009 -0300 summary: v4l2-spec: Fix xmlto compilation with some

  1   2   >