From: Hans de Goede <hdegoede@redhat.com>
To: David Ellingsworth <david@identd.dyndns.org>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
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 20:06:32 +0100 [thread overview]
Message-ID: <4BA3CB38.4090903@redhat.com> (raw)
In-Reply-To: <30353c3d1003190849v35b57dcai9ab11ff1362b4f46@mail.gmail.com>
Hi,
On 03/19/2010 04:49 PM, 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.
Ack, which is why I've been working actively on moving them all over to
gspca, but I need hardware access for that, see below.
However this thread is about removing support for v4l1 applications, and
there are actually still quite a few v4l1 apps out there, so we should
not do that!
> 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. I happen to have a USB
> camera which is supposedly supported by the ibmcam driver.
> 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.
Great! I've bene looking for someone with such a cam. As you may know
I've been slowly porting over all the remaining v4l1 usb webcam drivers
to gspca (removing a lot of code duplication and making them v4l2 drivers).
By far the easiest way to get the driver for this camera converted to
a gspca using v4l2 driver is to send it to me, would you be willing to
do that ?
Regards,
Hans
next prev parent reply other threads:[~2010-03-19 19:05 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
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 [this message]
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=4BA3CB38.4090903@redhat.com \
--to=hdegoede@redhat.com \
--cc=david@identd.dyndns.org \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.