Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: saaguirre@ti.com
Cc: linux-omap@vger.kernel.org
Subject: OMAP camera with BT-656 sensor
Date: Mon, 27 Jul 2009 13:10:54 -0600	[thread overview]
Message-ID: <4A6DFBBE.6020805@mlbassoc.com> (raw)
In-Reply-To: <a187869d0907271146q66112fc8l85aa37c8b1512d68@mail.gmail.com>

Sergio,

I'm trying to use your tree with a BT-656 style sensor(*).  I've
managed to get this [more or less] working when I use the official
TI PSP tree + OMAP3 patches, but I'm not getting very far with
your code.  I just updated my copy from your tree, but I don't
see any real changes since June 18 when I first started looking
at this.

I've made a number of changes, inspired by the PSP code to get
the BT-656 handling enabled in the CCDC.  I do see that the PSP
codebase seems older than yours? but is more complete in other
respects.  Can you enlighten me as to the heritage of these
different trees?

The problem I have at the moment is that sensor data is getting
into the CCDC module, but since the previewer/resizer modules
are not used, nothing is ever delivered to my user code.

Bottom line, I'm confused as to how I should go about getting
my driver/system working.  Do I use your work, or just stick
with the PSP base (why?)??

Thanks

(*) I cloned: git://dev.omapzoom.org/pub/scm/saaguirre/linux-omap-camera.git

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

  reply	other threads:[~2009-07-27 19:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 12:46 Camera Interface VS/HS Issue matthias schwarz
2009-07-27 13:05 ` Aguirre Rodriguez, Sergio Alberto
2009-07-27 13:09   ` matthias schwarz
2009-07-27 13:27     ` Aguirre Rodriguez, Sergio Alberto
2009-07-27 13:32       ` matthias schwarz
2009-07-27 14:25         ` matthias schwarz
2009-07-27 15:49           ` Aguirre Rodriguez, Sergio Alberto
2009-07-27 15:59             ` matthias schwarz
2009-07-27 16:08               ` Aguirre Rodriguez, Sergio Alberto
2009-07-27 16:11                 ` matthias schwarz
2009-07-27 16:21                   ` Aguirre Rodriguez, Sergio Alberto
2009-07-27 17:36                     ` matthias schwarz
2009-07-27 17:52                       ` Aguirre Rodriguez, Sergio Alberto
     [not found]                         ` <a187869d0907271145i177dcf52jb75aee758300878@mail.gmail.com>
2009-07-27 18:46                           ` matthias schwarz
2009-07-27 19:10                             ` Gary Thomas [this message]
2009-07-27 19:51                               ` OMAP camera with BT-656 sensor Aguirre Rodriguez, Sergio Alberto
2009-07-27 19:59                                 ` Gary Thomas
2009-07-27 20:14                                   ` Aguirre Rodriguez, Sergio Alberto
2009-07-28  4:14                                     ` Hiremath, Vaibhav
2009-07-28 12:44                                       ` Gary Thomas
2009-07-29  4:54                                         ` Hiremath, Vaibhav
2009-07-28  9:19                             ` Camera Interface VS/HS Issue matthias schwarz

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=4A6DFBBE.6020805@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=saaguirre@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