public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
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 19:52:00 -0300	[thread overview]
Message-ID: <4B9AC590.3020408@redhat.com> (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

All the above are webcam drivers. I doubt that those drivers would work
with tvtime: this software were meant to test the Vector's deinterlacing
algorithms, so it requires some specific video formats/resolutions found on TV
and require 25 or 30 fps, as far as I remember. For example, It doesn't support
QCIF/QVGA cameras.

If you want to extend tvtime to use webcams, some work is needed. Probably the easiest
way would be to use libv4l, that also does the V4L1 conversion, if needed. This may
actually make sense even for a few TV cards like em28xx, where you could use a bayer
format with a lower color depth and/or lower resolution, in order to allow viewing two 
simultaneous streams.

So, I suggest you to just drop V4L1 from tvtime and convert it to use libv4l (the conversion
is trivial: just replace open/close/ioctl from the V4L2 driver to the libv4l ones). This will
allow you to drop the old V4L1 driver from it, and, if you decide later to accept other
resolutions and make it more webcam friendly, you'll just need to allow tvtime to accept
other video resolutions and disable the de-interlacing setup if a webcam is detected.

-- 

Cheers,
Mauro

  parent reply	other threads:[~2010-03-12 22:52 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 [this message]
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=4B9AC590.3020408@redhat.com \
    --to=mchehab@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