From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Igor Kugasyan <kugasyan@hotmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: mt9v034 driver
Date: Wed, 17 Apr 2013 16:15:59 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1304171609080.16330@axis700.grange> (raw)
In-Reply-To: <DUB112-W5AD3C17EE426206DFAEF9D2CE0@phx.gbl>
Hi Igor
(forwarding to the real media Mailing List)
On Wed, 17 Apr 2013, Igor Kugasyan wrote:
> Dear Mr. Guennadi,
>
> Please tell me can I use the soc_camera_ (soc_camera.h, soc_camera.c)
> interface for a mt9v034 driver as a mt9v022 driver or not?
I don't know anything about mt9v034. It might or might not be compatible
with one of supported cameras. If it isn't, a new driver has to be
developed.
> I've read your Video4Linux soc-camera subsystem document and not found a mt9v034 among client drivers.
> I have the Leopard Board 368 (LI-TB02) with the WVGA camera
No, you cannot use soc-camera with Leopard Board. Its camera interface
might be supported by some other driver, but I'm not sure about that.
> LI-VM34LP but I haven't a mt9v034 driver for my camera
> for the linux-2.6.32 kernel with RidgeRun
Don't think there's anything that can be done with any kernel apart from
the current -next, i.e. the forthcoming 3.10.
> 2011Q2 SDK for LeopardBoardDM365 and
> dvsdk_dm365-evm_4_02_00_06. I haven't sufficient experience for
> comprehension but I learn...
The only possibility I see is to use a current kernel, adapt an existing
or write a new camera sensor driver for mt9v034 and use it with the
appropriate SoC camera interface driver.
Thanks
Guennadi
> Please,
> please, help me to solve this problem.
>
> Thanks
> in advance.
>
>
>
> Best regards,
>
>
>
> Sincerely
> yours
>
> Igor Kugasyan
>
> CONECS SSRE
>
> Lviv 79060
>
> Naukova 7
>
> Ukraine
>
>
>
> T +38 032 2952597
>
> F +38 032 2954879
>
> E dndp@conecs.lviv.ua
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next parent reply other threads:[~2013-04-17 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DUB112-W5AD3C17EE426206DFAEF9D2CE0@phx.gbl>
2013-04-17 14:15 ` Guennadi Liakhovetski [this message]
2013-04-18 14:05 ` mt9v034 driver Laurent Pinchart
[not found] <DUB112-W1120C7E0BD196DF8764BA21D2B70@phx.gbl>
2013-04-28 21:08 ` Laurent Pinchart
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=Pine.LNX.4.64.1304171609080.16330@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=kugasyan@hotmail.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