Ok, a couple of things have become clearer to me, some others managed to
confuse me again:
On Wed, 10 Jun 2009, Hans Verkuil wrote:
> On Wednesday 10 June 2009 18:02:39 Guennadi Liakhovetski wrote:
[snip]
> > which I now interpret as
> >
> > S_FMT(640x480) means "scale whatever rectangle has b
On Wed, 10 Jun 2009, Hans Verkuil wrote:
> On Wednesday 10 June 2009 18:02:39 Guennadi Liakhovetski wrote:
> >
> > {G,S,TRY}_FMT configure output geometry in user pixels
> > [GS]_CROP, CROPCAP configure input window in sensor pixels
>
> Agreed.
Now one more related question: if the driver (stack
On Wed, 10 Jun 2009, Hans Verkuil wrote:
> On Wednesday 10 June 2009 18:02:39 Guennadi Liakhovetski wrote:
> > This question - how S_FMT and S_CROP affest image geometry - has been
> > discussed at least twice before - that's only with my participation,
> > don't know if and how often it has come u
On Wednesday 10 June 2009 18:02:39 Guennadi Liakhovetski wrote:
> This question - how S_FMT and S_CROP affest image geometry - has been
> discussed at least twice before - that's only with my participation,
> don't know if and how often it has come up before. But the fact, that in
> two discussions
This question - how S_FMT and S_CROP affest image geometry - has been
discussed at least twice before - that's only with my participation, don't
know if and how often it has come up before. But the fact, that in two
discussions we came up with different results seems to suggest, that this
is no
