public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Akey <akeym@onid.orst.edu>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>,
	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: Fri, 12 Mar 2010 14:20:44 -0800	[thread overview]
Message-ID: <4B9ABE3C.6010909@onid.orst.edu> (raw)
In-Reply-To: <201003122242.06508.hverkuil@xs4all.nl>

Hans Verkuil wrote:
> On Friday 12 March 2010 21:11:49 Devin Heitmueller wrote:
>   
>> Hello,
>>
>> I know some months ago, there was some discussion about a few drivers
>> which were stragglers and had not been converted from V4L to V4L2.
>>
>> Do we have a current list of driver which still haven't been converted?
>>     
>
> These drivers are still v4l1:
>
> arv
> bw-qcam
> c-qcam
> cpia_pp
> cpia_usb
> ov511
> se401
> stradis
> stv680
> usbvideo
> w9966
>
> Some of these have counterparts in gspca these days so possibly some drivers
> can be removed by now. Hans, can you point those out?
>
> arv, bw-qcam, c-qcam, cpia_pp and stradis can probably be moved to staging
> and if no one steps up then they can be dropped altogether.
>   

Does this mean that the bw-qcam driver will be removed in future 
revisions or does this mean it will just never be updated to v4l2?

> According to my notes I should be able to test cpia_usb. I would have to
> verify that, though. I think it is only used in a USB microscope. It is
> effectively a webcam. I can also test usbvideo (USB 1 TV capture device).
> The latter is probably the most important driver that needs converting,
> because I think these are not uncommon.
>
> However, I have no time to work on such a driver conversion. But if someone
> is seriously willing to put time and effort in that, then I am willing to
> mail the hardware.
>
>   
>> I started doing some more tvtime work last night, and I would *love*
>> to drop V4L support (and *only* support V4L2 devices), since it would
>> make the code much cleaner, more reliable, and easier to test.
>>
>> If there are only a few obscure webcams remaining, then I'm willing to
>> tell those users that they have to stick with whatever old version of
>> tvtime they've been using since the last release four years ago.
>>     
>
> To my knowledge the usbvideo driver is probably the least obscure device
> that is still using V4L1.
>
> Regards,
>
> 	Hans
>
>   


  reply	other threads:[~2010-03-12 22:26 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 [this message]
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

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=4B9ABE3C.6010909@onid.orst.edu \
    --to=akeym@onid.orst.edu \
    --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