From: Gary Thomas <gary@mlbassoc.com>
To: Enrico <ebutera@users.berlios.de>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Subject: Re: [RFC 0/3] omap3isp: add BT656 support
Date: Wed, 12 Oct 2011 06:15:09 -0600 [thread overview]
Message-ID: <4E9584CD.5080107@mlbassoc.com> (raw)
In-Reply-To: <CA+2YH7vT441UMdawQY=N=4Fa7d9cYejwE4iYd8Sz7aE5NCJf2w@mail.gmail.com>
On 2011-10-12 02:07, Enrico wrote:
> On Wed, Oct 12, 2011 at 12:34 AM, Gary Thomas<gary@mlbassoc.com> wrote:
>> On 2011-10-11 16:25, Enrico wrote:
>>>
>>> On Wed, Oct 12, 2011 at 12:04 AM, Gary Thomas<gary@mlbassoc.com> wrote:
>>>>
>>>> Sorry, this just locks up on boot for me, immediately after finding the
>>>> TVP5150.
>>>> I applied your changes to the above tree
>>>> commit 658d5e03dc1a7283e5119cd0e9504759dbd3d912
>>>> Author: Laurent Pinchart<laurent.pinchart@ideasonboard.com>
>>>> Date: Wed Aug 31 16:03:53 2011 +0200
>>>
>>> Did you add Javier patches for the tvp5150?
>>
>> No, I thought your set was self-contained. I'll add them now.
>>
>>>
>>>> However, it does not build for my OMAP3530 without the attached patches.
>>>
>>> I can't remember now if i had omap vout enabled in my kernel config
>>> but that one in ispccdc.c is strange, tomorrow i will do again a clean
>>> rebuild.
>>
>> I can't see how to turn off omap_vout
>
> In multimedia/video capture/omap2 video4linux
>
> I had it disabled and enabling it gave me an error too, but it's not
> something that is changed by my patches so it is broken in the -yuv
> tree.
>
> I made a distclean rebuild and i don't have any errors, are you sure
> you need that include in ispccdc.c?
Yes, I started from a 100% clean build + tree. Without that change,
I get a compile error. With it, and the TVP patches, I can now grab
some video from my camera.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-10-12 12:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 15:08 [RFC 0/3] omap3isp: add BT656 support Enrico Butera
2011-10-11 15:08 ` [RFC 1/3] omap3isp: ccdc: Add interlaced field mode to platform data Enrico Butera
2011-10-11 15:08 ` [RFC 2/3] omap3isp: ispvideo: export isp_video_mbus_to_pix Enrico Butera
2011-10-11 15:08 ` [RFC 3/3] omap3isp: ispccdc: configure CCDC registers and add BT656 support Enrico Butera
2011-10-11 22:04 ` [RFC 0/3] omap3isp: " Gary Thomas
2011-10-11 22:25 ` Enrico
2011-10-11 22:34 ` Gary Thomas
2011-10-11 22:36 ` Gary Thomas
2011-10-11 22:48 ` Enrico
2011-10-12 8:07 ` Enrico
2011-10-12 12:15 ` Gary Thomas [this message]
2011-10-13 15:04 ` Javier Martinez Canillas
2011-10-27 16:16 ` Enrico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E9584CD.5080107@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ebutera@users.berlios.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox