] On Behalf Of Karicheri, Muralidharan
Sent: 2009年9月28日 23:41
To: Karicheri, Muralidharan; Yu, Jinlu; Mauro Carvalho Chehab
Cc: linux-media@vger.kernel.org
Subject: RE: [PATCH 0/5] V4L2 patches for Intel Moorestown Camera Imaging
Forgot to add disclaimer...
These are just my opinion based on the
: 8758 1603
TEL: 86 10 8217 1603
FAX: 86 10 8286 1400
-Original Message-
From: linux-media-ow...@vger.kernel.org
[mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Yu, Jinlu
Sent: 2009年9月27日 22:31
To: Mauro Carvalho Chehab
Cc: linux-media@vger.kernel.org
Subject: RE: [PATCH 0/5] V
sync polarity
edge; sampling edge
Best Regards
Jinlu Yu
UMG UPSG PRC
INET: 8758 1603
TEL: 86 10 8217 1603
FAX: 86 10 8286 1400
-Original Message-
From: Mauro Carvalho Chehab [mailto:mche...@infradead.org]
Sent: 2009年9月24日 19:45
To: Yu, Jinlu
Cc: linux-media@vger.kernel.org
Subject: Re
About S_FMT, Moorestown Camera driver which I am working on has a different
story.
We do use different sensor resolutions, because high resolution has low FPS,
and can not be used for view-finding, e.g. ov5630 only output 15fps with 5Mega
resolution.
Our current solution is to disable the sca
Hi, Hans/Guennadi
I am modifying these drivers to comply with v4l2 framework. I have finished
replacing our buffer managing code with utility function from videobuf-core.c
and videobuf-dma-contig.c. Now I am working on the subdev. One thing I am sure
is that each sensor should be registered as
