public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: David Ellingsworth <david@identd.dyndns.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	v4l-dvb <linux-media@vger.kernel.org>
Subject: Re: RFC: Drop V4L1 support in V4L2 drivers
Date: Fri, 19 Mar 2010 14:43:05 -0300	[thread overview]
Message-ID: <4BA3B7A9.2050405@redhat.com> (raw)
In-Reply-To: <30353c3d1003190849v35b57dcai9ab11ff1362b4f46@mail.gmail.com>

David Ellingsworth wrote:
> On Fri, Mar 19, 2010 at 9:47 AM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>> The V4L1 drivers that lasts are the ones without maintainers and probably without
>> a large users base. So, basically legacy hardware. So, their removals make sense.
>>
> 
> In many ways the above statement is a catch 22. Most, if not all the
> v4l1 drivers are currently broken or unmaintained. However, this does
> not mean there are users who would not be using these drivers if they
> actually worked or had been properly maintained. I know this to be a
> fact of the ibmcam driver. It is both broken and unmaintained. Because
> of this I'm sure no one is currently using it.

It makes sense. However, considering that no new V4L1 driver is committed
since 2006, this means that those are old drivers for old hardware.

> I happen to have a USB
> camera which is supposedly supported by the ibmcam driver.

In the specific case of ibmcam, we had only 10 commits on -hg since its
addition, back in 2006.

Just using it as an example about the remaining drivers, for today's hardware,
an ibmusb model 3 webcam has 640x480x3fps, according to his driver. Other models
have QCIF or QVGA as their maximum resolution. I can easily buy a 640x480x30fps
camera (or even something better than that) for US$12,00 on a close shopping.

So, even if the driver would be 100% functional, I doubt that you would find too
many users of this webcam, simply because people would need a faster frame rate
or wanted a higher resolution.

> Unfortunately, I have not the time nor expertise needed to
> update/fix/replace this driver, though I have previously tried. If
> someone on this list is willing to collaborate with me to make a
> functional v4l2 driver to replace the existing ibmcam driver, I'd be
> more than willing to expend more time and energy in doing so.
> Hopefully someday I'll actually be able to use the camera that I own,
> considering as is it barely works under Windows.

I agree that it would be interesting to port it to V4L2, instead of just
dropping it. Maybe Hans Geode or someone else with some spare time
could help you on this task.

-- 

Cheers,
Mauro

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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  7:59 RFC: Drop V4L1 support in V4L2 drivers Hans Verkuil
2010-03-19  8:04 ` Laurent Pinchart
2010-03-19  8:46   ` Hans Verkuil
2010-03-19  8:50     ` Laurent Pinchart
2010-03-19  9:03     ` Markus Rechberger
2010-03-19 13:47     ` Mauro Carvalho Chehab
2010-03-19 15:49       ` David Ellingsworth
2010-03-19 17:43         ` Mauro Carvalho Chehab [this message]
2010-03-19 18:00           ` David Ellingsworth
2010-03-19 18:12             ` Devin Heitmueller
2010-03-19 19:04               ` VDR User
2010-03-20  1:01                 ` hermann pitton
2010-03-19 19:57             ` Mauro Carvalho Chehab
2010-03-19 19:06         ` Hans de Goede
2010-03-19 15:17     ` Andy Walls
2010-03-19 19:02     ` Hans de Goede
2010-03-19 13:01 ` Mauro Carvalho Chehab
2010-03-19 19:10   ` Hans de Goede
2010-03-19 19:27     ` Mauro Carvalho Chehab

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=4BA3B7A9.2050405@redhat.com \
    --to=mchehab@redhat.com \
    --cc=david@identd.dyndns.org \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --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