From: TJ <one.timothy.jones@gmail.com>
To: Pete Eberlein <pete@sensoray.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: go7007 driver -- which program you use for capture
Date: Thu, 14 Jan 2010 15:18:25 -0500 [thread overview]
Message-ID: <4B4F7C11.3030802@gmail.com> (raw)
In-Reply-To: <1263499712.4730.11.camel@pete-desktop>
Pete Eberlein wrote:
> On Thu, 2010-01-14 at 15:03 -0500, TJ wrote:
>
>> Pete, Question: I was looking through the code and noticed that you turned s2250
>> driver into v4l2_subdev and go7007 driver initializes it as such and passes it
>> calls via call_all (v4l2_device_call_until_err). How does that affect other
>> drivers? Does that mean they all need to re-written as v4l2_subdev?
>
> That is correct. The other drivers do not work until they are all
> converted to the subdev interface. I'm working on the other drivers
> now. I've finished ov7640 and have started on saa7113.
>
> Once the subdev driver conversions are completed, we should be able to
> move the go7007 driver out of staging.
>
> Pete
>
Cool man. I will start working on tw9903 and tw9906, as this is my main area of
interest. Is there a template for subdev driver or should I just use your s2250
as an example? -TJ
next prev parent reply other threads:[~2010-01-14 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 19:07 go7007 driver -- which program you use for capture TJ
2010-01-08 20:17 ` Jarod Wilson
2010-01-08 22:25 ` TJ
2010-01-13 21:02 ` Mauro Carvalho Chehab
2010-01-13 22:04 ` TJ
2010-01-13 22:12 ` Mauro Carvalho Chehab
2010-01-14 20:03 ` TJ
2010-01-14 20:08 ` Pete Eberlein
2010-01-14 20:18 ` TJ [this message]
2010-01-12 23:46 ` Pete Eberlein
2010-01-13 21:51 ` TJ
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=4B4F7C11.3030802@gmail.com \
--to=one.timothy.jones@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=pete@sensoray.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