public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Németh Márton" <nm127@freemail.hu>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Jean-Francois Moine <moinejf@free.fr>,
	Thomas Kaiser <thomas@kaiser-linux.li>,
	linux-media@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND][PATCH 1/2] v4l2: modify the webcam video standard handling
Date: Mon, 31 Aug 2009 07:55:50 +0200	[thread overview]
Message-ID: <4A9B65E6.5070005@freemail.hu> (raw)
In-Reply-To: <20090830234114.16b90c36@pedra.chehab.org>

Hi,

first of all thank you for your detailed answer.

Mauro Carvalho Chehab wrote:
> Hi Németh,
> 
> Em Sun, 23 Aug 2009 11:30:42 +0200
> Németh Márton <nm127@freemail.hu> escreveu:
> 
>> From: Márton Németh <nm127@freemail.hu>
>>
>> Change the handling of the case when vdev->tvnorms == 0.
>>
> 
> This patch (together with a few others related to tvnorms and camera drivers)
> reopens an old discussion: should webcams report a tvnorm?
> 
> There's no easy answer for it since:
> 
> 1) removing support for VIDIOC_G_STD/VIDIOC_S_STD causes regressions, since
> some userspace apps stops working;
> 
> 2) It is a common scenario to use cameras connected to some capture only devices
> like several bttv boards used on surveillance systems. Those drivers report STD,
> since they are used also on TV;
> 
> 3) There are even some devices that allows cameras to be connected to one input and
> TV on another input. This is another case were the driver will report a TV std;
> 
> 4) Most webcam formats are based on ITU-T formats designed to be compatible
> with TV (formats like CIF and like 640x480 - and their multiple/sub-multiples);
> 
> 5) There are formats that weren't originated from TV on some digital webcams,
> so, for those formats, it makes no sense to report an existing std.
> 
> Once people proposed to create an special format for those cases
> (V4L2_STD_DIGITAL or something like that), but, after lots of discussions,
> no changes were done at API nor at the drivers.
> 
> While we don't have an agreement on this, I don't think we should apply a patch
> like this.

I was reading the V4L2 specification and based my patch on the specification.

Maybe the specification is wrong at that point? (see Chapter 1.7 Video Standards
at http://v4l2spec.bytesex.org/spec/x448.htm , starting with paragraph 6:
"Special rules apply to USB cameras...")

Regards,

	Márton Németh


  reply	other threads:[~2009-08-31  5:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  6:17 [PATCH 1/2] v4l2: modify the webcam video standard handling Németh Márton
2009-08-23  9:30 ` [RESEND][PATCH " Németh Márton
2009-08-31  2:41   ` Mauro Carvalho Chehab
2009-08-31  5:55     ` Németh Márton [this message]
2009-08-31  6:58     ` Laurent Pinchart
2009-08-31  7:33       ` Hans Verkuil
2009-08-31 13:08         ` Mauro Carvalho Chehab
2009-08-31 14:44           ` Hans Verkuil
2009-08-31 13:03       ` Mauro Carvalho Chehab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A9B65E6.5070005@freemail.hu \
    --to=nm127@freemail.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=moinejf@free.fr \
    --cc=thomas@kaiser-linux.li \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox