From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: atmel v4l2 soc driver
Date: Mon, 23 Mar 2009 17:14:52 +0100 [thread overview]
Message-ID: <49C7B57C.7040809@atmel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0903231705080.6370@axis700.grange>
Well I am confused now...Should I still convert the atmel ISI driver to
a soc driver?
My concern was not to release a driver for the ov9655, but to have one
which is working so I could test my atmel-soc driver :)
Because I only have an ov9655 sensor here...
Regards
Sedji
Guennadi Liakhovetski a écrit :
> On Mon, 23 Mar 2009, Sedji Gaouaou wrote:
>
>> Guennadi Liakhovetski a écrit :
>>> Wouldn't ov9655 be similar enough to ov9650 as used in stk-sensor.c? Hans,
>>> would that one also be converted to v4l2-device? If so, Sedji, you don't
>>> need to write yet another driver for it.
>> I had a look at the stk-sensor file. Does it follow the soc arch?
>
> No, it does not. But soc-camera is going to be converted to v4l2-device,
> so, if stkweb is going to be converted too, then the driver will be
> re-used.
>
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
>
next prev parent reply other threads:[~2009-03-23 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 9:52 atmel v4l2 soc driver Sedji Gaouaou
2009-03-11 10:02 ` Guennadi Liakhovetski
2009-03-23 15:21 ` Sedji Gaouaou
2009-03-23 15:40 ` Guennadi Liakhovetski
2009-03-23 16:00 ` Sedji Gaouaou
2009-03-23 16:06 ` Guennadi Liakhovetski
2009-03-23 16:14 ` Sedji Gaouaou [this message]
2009-03-23 16:30 ` Guennadi Liakhovetski
2009-08-03 7:13 ` Guennadi Liakhovetski
[not found] ` <4AFC15E6.2000101@atmel.com>
2009-11-12 14:12 ` Guennadi Liakhovetski
2009-03-23 18:23 ` Hans Verkuil
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=49C7B57C.7040809@atmel.com \
--to=sedji.gaouaou@atmel.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--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