public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Cohen <david.cohen@indt.org.br>
To: "ext Zhang, Jian" <jzhang@ti.com>
Cc: Linux-omap-open-source@linux.omap.com
Subject: Re: omap24xxcam status (Was: v4l2 camera test app)
Date: Mon, 20 Mar 2006 13:36:12 -0400	[thread overview]
Message-ID: <441EE80C.6000503@indt.org.br> (raw)
In-Reply-To: <304D2A85A9643F4A991BDDF8D297BBA602A10CB5@dlee05.ent.ti.com>

Yes... good point. I will genereted another patch with support to this
new interface.
But it would be great if anyone could test this patch on H4.

Regards,

David Cohen

ext Zhang, Jian wrote:

>David,
>
>I don't see the new sensor interface incorporated in your patch. It is
>likely that Micron 2MP camera MT9D111 will be used by more people. The
>new sensor interface supports double-context which is an advanced
>feature of micron camera.
>
>Regards,
>Jian    
>
>-----Original Message-----
>From: David Cohen [mailto:david.cohen@indt.org.br] 
>Sent: Monday, March 20, 2006 10:10 AM
>To: ext Komal Shah
>Cc: Ola Helm; Linux-omap-open-source@linux.omap.com; Zhang, Jian
>Subject: Re: omap24xxcam status (Was: v4l2 camera test app)
>
>Hi,
>
>I just sent a code that should be compilable and working. I guess the
>mainly target is to apply this patch to the public tree. After that, as
>Komal said, could be interesting to update the dma code to the omap api
>to be easier future reviews.
>
>Regards,
>
>David Cohen
>
>ext Komal Shah wrote:
>
>  
>
>>--- Ola Helm <ola.hel@gmail.com> wrote:
>>
>> 
>>
>>    
>>
>>>Hi,
>>>
>>>Have you got some idea what's the situation of the 24xx camera driver
>>>at the
>>>moment? AFAIK the patch David sent in last month is not included to
>>>tree,
>>>propably since there were some opposite opinions about the way of
>>>implementation and at least I did not have one file mentioned in
>>>patch (I
>>>think you mentioned about the same issue)
>>>   
>>>
>>>      
>>>
>>24xx camera driver is now in David's hand. I just review the code now,
>>as not able to work on camera stuff anymore.
>>
>>Following strategy can work out meanwhile as I had offline discussion
>>with David :)
>>
>>o Separate 24xx CamDMA code from omap24xxcam.c to new file as 
>> exported apis (Suggested by David)
>>
>>o Keep the old omap24xxcam driver interface(2.6.8 TI kernel days), 
>> having video out code part of the camera driver itself. As new 
>> separated video out code depends upon the common display controller  
>> library, which requires to change fb driver in git tree to adopt 
>> that interface, so that video out, and fb driver can 
>> utilize the same code. But video out patches submitted by me didn't 
>> generated any discussion on the list in that direction. 
>>
>>o So, to have 24xx camera code in git tree, we can use the old camera 
>> driver interface as of now, if everyone agrees.
>>
>>---Komal Shah
>>http://komalshah.blogspot.com/
>>
>>__________________________________________________
>>Do You Yahoo!?
>>Tired of spam?  Yahoo! Mail has the best spam protection around 
>>http://mail.yahoo.com 
>> 
>>
>>    
>>
>
>  
>

  reply	other threads:[~2006-03-20 17:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 16:27 omap24xxcam status (Was: v4l2 camera test app) Zhang, Jian
2006-03-20 17:36 ` David Cohen [this message]
2006-03-20 21:20 ` [PATCH] " David Cohen
2006-03-21 12:56   ` Komal Shah
2006-03-21 13:23     ` David Cohen
2006-03-21 13:30       ` Komal Shah
  -- strict thread matches above, loose matches on Subject: below --
2006-03-20 13:19 v4l2 camera test app Ola Helm
2006-03-20 14:58 ` omap24xxcam status (Was: v4l2 camera test app) Komal Shah
2006-03-20 16:10   ` David Cohen

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=441EE80C.6000503@indt.org.br \
    --to=david.cohen@indt.org.br \
    --cc=Linux-omap-open-source@linux.omap.com \
    --cc=jzhang@ti.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