linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] Adding YUV input support for OMAP3ISP driver
Date: Thu, 19 Jan 2012 07:36:41 -0700	[thread overview]
Message-ID: <4F182A79.6000603@mlbassoc.com> (raw)
In-Reply-To: <CAAwP0s3_U1tzRM3TcW+hGCVvm+aowwO9f6g6t8_pvZSJxyMrgA@mail.gmail.com>

On 2012-01-19 07:11, Javier Martinez Canillas wrote:
> On Thu, Jan 19, 2012 at 2:35 PM, Gary Thomas<gary@mlbassoc.com>  wrote:
>> On 2012-01-19 06:28, Laurent Pinchart wrote:
>>>
>>> Hi Gary,
>>>
>>> On Thursday 19 January 2012 14:13:53 Gary Thomas wrote:
>>>>
>>>> On 2012-01-19 05:50, Laurent Pinchart wrote:
>>>>>
>>>>> On Thursday 19 January 2012 13:41:57 Gary Thomas wrote:
>>>>>>
>>>>>> On 2012-01-17 08:33, Laurent Pinchart wrote:
>>>>>>       <snip>
>>>>>>>
>>>>>>>
>>>>>>> I already had a couple of YUV support patches in my OMAP3 ISP tree at
>>>>>>> git.kernel.org. I've rebased them on top of the lastest V4L/DVB tree
>>>>>>> and pushed them to
>>>>>>>
>>>>>>> http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp
>>>>>>> - omap3isp-yuv. Could you please try them, and see if they're usable
>>>>>>> with your sensor ?
>>>>>>
>>>>>>
>>>>>> I just tried this kernel with my board.  The media control
>>>>>> infrastructure comes up and all of the devices are created, but I can't
>>>>>> access them.
>>>>>>
>>>>>>    From the bootup log:
>>>>>>      Linux media interface: v0.10
>>>>>>      Linux video capture interface: v2.00
>>>>>
>>>>>
>>>>> Any message from the omap3isp driver and from the sensor driver ?
>>>>
>>>>
>>>> No, it doesn't appear that the sensor was probed (or maybe it failed but
>>>> no messages).  I'll check into this.
>>>
>>>
>>> Is the omap3-isp driver compiled as a module ? If so, make sure iommu2.ko
>>> is
>>> loaded first. 'rmmod omap3-isp&&    modprobe iommu2&&    modprobe omap3-isp'
>>> is a
>>>
>>> quick way to test it.
>>
>>
>> I have everything compiled in - no modules.
>>
>
> At least for me, it only worked when compiled both the omap3-isp and
> tvp5150 drivers as a module. If I compile them built-in, it fails.

Can you share your board/sensor init code from your board-init.c
so I can see how to manage this as a module?

n.b. I really don't like messing with modules - it used to work
fine, so IMO it should continue to do so.

Thanks


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

  reply	other threads:[~2012-01-19 14:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EBE38CF866F2F94F95FA9A8CB3EF2284069CAE@singex1.aptina.com>
2012-01-17 15:33 ` [PATCH] Adding YUV input support for OMAP3ISP driver Laurent Pinchart
2012-01-19 12:41   ` Gary Thomas
2012-01-19 12:50     ` Laurent Pinchart
2012-01-19 13:13       ` Gary Thomas
2012-01-19 13:28         ` Laurent Pinchart
2012-01-19 13:35           ` Gary Thomas
2012-01-19 13:52             ` Gary Thomas
2012-01-19 14:17               ` Enrico
2012-01-20 12:19                 ` Laurent Pinchart
2012-01-30 17:30                   ` Gary Thomas
2012-02-04 11:48                     ` Gary Thomas
2012-02-04 15:26                       ` Enrico
2012-03-08 15:04                         ` Enrico
2012-01-19 14:11             ` Javier Martinez Canillas
2012-01-19 14:36               ` Gary Thomas [this message]
2012-01-19 16:12                 ` Javier Martinez Canillas
2012-01-19 17:08                 ` Gary Thomas
2012-01-19 17:22                   ` Gary Thomas
2012-01-19 17:39                     ` Gary Thomas

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=4F182A79.6000603@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=martinez.javier@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).