On Fri, Sep 25, 2009 at 3:07 AM, Guennadi Liakhovetski
g.liakhovet...@gmx.de wrote:
Hi Hans
Thanks for keeping us updated. One comment:
On Wed, 23 Sep 2009, Hans Verkuil wrote:
In the afternoon we discussed the proposed timings API. There was no
opposition to this API. The idea I had to
On Sat, 26 Sep 2009, Dongsoo, Nathaniel Kim wrote:
On Fri, Sep 25, 2009 at 3:07 AM, Guennadi Liakhovetski
g.liakhovet...@gmx.de wrote:
Hi Hans
Thanks for keeping us updated. One comment:
On Wed, 23 Sep 2009, Hans Verkuil wrote:
In the afternoon we discussed the proposed timings
On Sat, Sep 26, 2009 at 6:32 PM, Guennadi Liakhovetski
g.liakhovet...@gmx.de wrote:
On Sat, 26 Sep 2009, Dongsoo, Nathaniel Kim wrote:
On Fri, Sep 25, 2009 at 3:07 AM, Guennadi Liakhovetski
g.liakhovet...@gmx.de wrote:
Hi Hans
Thanks for keeping us updated. One comment:
On Wed, 23
On Sat, Sep 26, 2009 at 6:32 PM, Guennadi Liakhovetski
g.liakhovet...@gmx.de wrote:
On Sat, 26 Sep 2009, Dongsoo, Nathaniel Kim wrote:
On Fri, Sep 25, 2009 at 3:07 AM, Guennadi Liakhovetski
g.liakhovet...@gmx.de wrote:
Hi Hans
Thanks for keeping us updated. One comment:
On Wed, 23
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
Hi Hans
Thanks for keeping us updated. One comment:
On Wed, 23 Sep 2009, Hans Verkuil wrote:
In the afternoon we discussed the proposed timings API. There was no
opposition to this API. The idea I had to also use this for sensor setup
turned out to be based on a misconception on how the
