From: Brian Johnson <brijohn@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Convert cpia driver to v4l2, drop parallel port version support?
Date: Wed, 17 Jun 2009 14:11:40 -0400 [thread overview]
Message-ID: <4A3931DC.1060003@gmail.com> (raw)
In-Reply-To: <4A390093.5090003@redhat.com>
Hans de Goede wrote:
>>> sn9c102
>>> Supports a large number of cams also supported by gspca's sonixb / sonixj driver, we're using
>>> #ifdef .... macros to detect if both are being build at the same time to include usb-id's only
>>> in one of the 2.
>> Btw, it would be interesting to work with the out-of-tree microdia driver,
>> since there are some models that are supported only by the alternative driver.
>
> Ack, only one small problem, which is another reason why Luca's drivers should slowly be phased
> out, Luca has gone closed source with his sn9cxxx driver.
>
> There is an out of tree driver for the new sn9c2xx models you talk about though, with active
> developers, I've pushing them to get it into the mainline, I'll give it another try soonish.
>
Hello I'm one of the developers for the current out of tree sn9c20x driver. What needs to be done in order
to get the sn9c20x code into the mainline? Am i right in assuming it would be preferred to move the code into
a sn9c20x gspca subdriver rather then include the complete out of tree driver? If this is the case I can work
on a set of patches to implement our code as a gspca subdriver.
Also i have a few questions regarding submitting the patches.
1) In addition to sending them to linux-media should I CC them to anyone in particular?
2) The entire patch would likely be about 70k. Should I just send one patch or split the
thing up into several?
Thanks,
Brian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-17 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 7:43 Convert cpia driver to v4l2, drop parallel port version support? Hans Verkuil
2009-06-17 9:34 ` Hans de Goede
2009-06-17 9:56 ` Mauro Carvalho Chehab
2009-06-17 10:00 ` Mauro Carvalho Chehab
2009-06-17 10:59 ` Hans de Goede
2009-06-17 14:28 ` Mauro Carvalho Chehab
2009-06-17 14:41 ` Hans de Goede
2009-06-17 15:23 ` Mauro Carvalho Chehab
2009-06-17 17:25 ` Hans de Goede
2009-06-17 18:11 ` Brian Johnson [this message]
2009-06-17 18:35 ` Hans de Goede
2009-06-17 10:56 ` Andy Walls
-- strict thread matches above, loose matches on Subject: below --
2009-06-17 11:26 Hans Verkuil
2009-06-17 13:29 ` Mauro Carvalho Chehab
2009-06-17 10:32 Hans Verkuil
2009-06-17 7:00 Hans de Goede
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=4A3931DC.1060003@gmail.com \
--to=brijohn@gmail.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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