Hi Florian,
On Friday 06 July 2012 11:55:40 Florian Neuhaus wrote:
> Hi Laurent,
>
> Laurent Pinchart wrote on 2012-07-05:
> > There's really an issue, which was introduced in v3.5-rc1. Could you
> > please try the following patch instead of yours ?
> >
> > diff --git a/drivers/media/video/omap3
Hi Laurent,
Laurent Pinchart wrote on 2012-07-05:
> There's really an issue, which was introduced in v3.5-rc1. Could you please
> try
> the following patch instead of yours ?
>
> diff --git a/drivers/media/video/omap3isp/isppreview.c
> b/drivers/media/video/omap3isp/isppreview.c index 9c6dd44..
Hi Florian,
On Thursday 05 July 2012 16:06:03 Florian Neuhaus wrote:
> Laurent Pinchart wrote on 2012-07-05:
> >> When I now capture a frame with yavta (see [3] for details), I must use
> >> 846x639 as frame size (as this size is reported by the driver). But it
> >> seems that the outputted image
Hi Laurent,
Laurent Pinchart wrote on 2012-07-05:
>> When I now capture a frame with yavta (see [3] for details), I must use
>> 846x639 as frame size (as this size is reported by the driver). But it
>> seems that the outputted image is 2px wider (that means 848x639). This
>> results in a "scramble
Hi Florian,
On Thursday 05 July 2012 12:28:04 Florian Neuhaus wrote:
> Dear all,
> I am trying to get a mt9p031 sensor running on a beagleboard-xm with the
> following configuration:
>
> Hardware:
> - beagleboard-xm, rev c1
> - Leopard Imaging cam module LI-5M03 with a mt9p031 5MP sensor
>
> Sof
