lkml.org 
[lkml]   [2009]   [Aug]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RESEND][PATCH 1/2] v4l2: modify the webcam video standard handling
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.



Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2009-08-31 04:45    [W:0.058 / U:2.328 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site