On Fri, Apr 17, 2015 at 4:39 AM, Laurent Pinchart
wrote:
> Hi Chris,
>
> On Thursday 16 April 2015 13:05:30 Chris Whittenburg wrote:
>> On Tue, Apr 7, 2015 at 10:51 AM, Laurent Pinchart wrote:
>> > Black level compensation is applied by the CCDC before writing raw frames
On Tue, Apr 7, 2015 at 10:51 AM, Laurent Pinchart
wrote:
> Black level compensation is applied by the CCDC before writing raw frames to
> memory. If your raw frames are correct BLC is probably not to blame.
>
> The default contrast is x1.0 and the default brightness is +0.0, so I don't
> think tho
On Tue, Apr 7, 2015 at 10:51 AM, Laurent Pinchart
wrote:
> I suspect the RGB2RGB conversion matrix to be wrong. The default setting is
> supposed to handle fluorescent lighting. You could try setting the RGB2RGB
> matrix to the identity matrix and see if this helps. See
> http://git.ideasonboard.o
Hi Sakari,
Thanks for the reply.
On Tue, Mar 24, 2015 at 6:51 PM, Sakari Ailus wrote:
> Do you know if the sensor has black level correction enabled? It appears to
> have one, but I'm not completely sure what it does there. I'd check that it
> is indeed enabled.
The ar0130cs does have black lev
We're working on a DM3730 platform running a 3.5.7 kernel, using the
pipeline below to take a 12-bit monochrome sensor (Aptina AR0130) and
convert it to UYVY format for use with the TI codecs.
In general, this works, but the images end up looking washed out.
Running them thru a "normalize" functio
I'm using a 3.0.17 kernel on a dm3730 with a custom 8-bit grayscale sensor.
When using a simple gstreamer pipeline to test:
gst-launch -v v4l2src device=/dev/video2 !
'video/x-raw-gray,bpp=(int)8,framerate=(fraction)10/1,width=640,height=480'
! fakesink
I get lots of calls to isp_video_try_forma
rt wrote:
>>>> On Saturday 25 February 2012 01:48:02 Sakari Ailus wrote:
>>>>> On Fri, Feb 17, 2012 at 05:32:31PM -0600, Chris Whittenburg wrote:
>>>>>> I fixed my sensor to respect a "run" signal from the omap, so that now
>>>>>>
fer?
Is there a way to determine if the CCDC is writing to memory or not?
Thanks for any points,
Chris
On Wed, Feb 15, 2012 at 11:29 AM, Chris Whittenburg
wrote:
> Maybe this is more of a OMAP specific question, but I'm using a
> beagleboard-xm with a custom image sensor on
Maybe this is more of a OMAP specific question, but I'm using a
beagleboard-xm with a custom image sensor on a 3.0.17 kernel.
Everything configures ok with:
media-ctl -r
media-ctl -l '"xrtcam 2-0048":0->"OMAP3 ISP CCDC":0[1]'
media-ctl -l '"OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]'
media-c
I'm using the 3.0.8 kernel, with a few changes to add support for
mt9p031 on a beagleboard xm.
I'm configuring with:
media-ctl -v -r -l '"mt9p031 2-0048":0->"OMAP3 ISP CCDC":0[1], "OMAP3
ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]'
media-ctl -v -f '"mt9p031 2-0048":0[SGRBG12 370x243], "OMAP3 ISP
C
I'm continuing my journey of adding mt9p031 (LI-5M03 board) into 3.0.7
kernel built using oe-core for a beagleboard-xm.
I'm down to starting yavta, but getting the error "Unable to start
streaming: 32."
The mt9p031 is detected correctly at boot.
Here are my setup commands:
media-ctl -v -r -l '"m
On Tue, Nov 8, 2011 at 6:42 AM, Laurent Pinchart
wrote:
> Hi Chris,
>
> On Tuesday 08 November 2011 03:03:43 Chris Whittenburg wrote:
>> On Mon, Nov 7, 2011 at 5:14 AM, Laurent Pinchart wrote:
>> > On Monday 07 November 2011 12:08:15 Gary Thomas wrote:
>> >> On
On Mon, Nov 7, 2011 at 5:14 AM, Laurent Pinchart
wrote:
> On Monday 07 November 2011 12:08:15 Gary Thomas wrote:
>> On 2011-11-06 15:26, Chris Whittenburg wrote:
>> > On Fri, Nov 4, 2011 at 6:49 AM, Laurent Pinchart wrote:
>> >> On Tuesday 25 October 2011 04
Hi Laurent,
On Fri, Nov 4, 2011 at 6:49 AM, Laurent Pinchart
wrote:
> Hi Chris,
>
> On Tuesday 25 October 2011 04:48:13 Chris Whittenburg wrote:
>> I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my
>> beagleboard-xm.
>
> You will need boar
I'm using oe-core to build the 3.0.7+ kernel, which runs fine on my
beagleboard-xm.
I'm interested in the media controller framework, which I believe is
in this kernel.
I expected there to be a /dev/media0, but it is not there. I do see
"Linux media interface: v0.10" in my dmesg log, so I know
m
15 matches
Mail list logo
