public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Hans de Goede <j.w.r.degoede@hhs.nl>
Subject: Re: Remaining drivers that aren't V4L2?
Date: Sat, 13 Mar 2010 20:44:58 +0100	[thread overview]
Message-ID: <4B9BEB3A.3010801@redhat.com> (raw)
In-Reply-To: <829197381003130623w22133c4eyadff26301381f8ca@mail.gmail.com>

Hi,

On 03/13/2010 03:23 PM, Devin Heitmueller wrote:
> On Sat, Mar 13, 2010 at 1:33 AM, Hans de Goede<hdegoede@redhat.com>  wrote:
>>> usbvideo
>>
>> This actually is a framework for usb video devices a bit like
>> gspca one could say. It supports the following devices:
>>
>> "USB 3com HomeConnect (aka vicam)"
>> "USB IBM (Xirlink) C-it Camera"
>> "USB Konica Webcam support"
>> "USB Logitech Quickcam Messenger"
>>
>> Of which the Logitech Quickcam Messenger has a gspca subdriver
>> now, and is scheduled for removal.
>
> Now that I see the product list, I realize that I actually have a 3com
> HomeConnect kicking around in a box.  So if nobody gets around to it,
> I could probably kill a few hours and do the conversion (given that
> was a fairly popular product at the time).
>
> Or would it be better to convert the products to gpsca (I don't
> actually know/understand if that's possible at this point)?
>

It would be much better to change it into a gspca subdriver, gspca is
a generic framework for usb webcams, and as such has a lot of code
which all these devices need shared in place, making the subdrivers
quite small, and nice to write as you can focus on the actual
camera specifics instead of on things like getting locking in case of
hot unplug while an app is streaming right.

Regards,

Hans

      reply	other threads:[~2010-03-13 19:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 20:11 Remaining drivers that aren't V4L2? Devin Heitmueller
2010-03-12 21:42 ` Hans Verkuil
2010-03-12 22:20   ` Michael Akey
2010-03-12 22:24     ` Devin Heitmueller
2010-03-12 22:32     ` Hans Verkuil
2010-03-12 22:52   ` Mauro Carvalho Chehab
2010-03-12 22:59     ` Devin Heitmueller
2010-03-12 23:35       ` Mauro Carvalho Chehab
2010-03-13  6:33   ` Hans de Goede
2010-03-13 10:03     ` Hans Verkuil
2010-03-13 14:23     ` Devin Heitmueller
2010-03-13 19:44       ` Hans de Goede [this message]

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=4B9BEB3A.3010801@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=hverkuil@xs4all.nl \
    --cc=j.w.r.degoede@hhs.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