public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: How to handle v4l1 -> v4l2 driver transition
Date: Wed, 17 Jun 2009 08:54:20 +0200	[thread overview]
Message-ID: <4A38931C.2060506@redhat.com> (raw)

Hi all,

I've recently been working on adding support for cams with the
ov511(+) and ov518(+) to the gspca ov519 driver. I'm happy to
announce that work is finished, see:
http://linuxtv.org/hg/~hgoede/gspca

And the pull request I just send. This does lead to the question
what to do with the existing  in kernel v4l1 ov511 driver, which
claims to support these 2 bridges too (but since the decompression
code has been removed actually only works with the 511 in uncompressed
mode).

It is clear that the ov518 usb-id's should be removed from the ov511
driver. But that still leaves the ov511 support, we could just completely
remove the ov511 driver, as the code in gspca should cover all supported
devices (and his been tested with a few).

However the downside of removing it is that people who used to have
a working ov511 setup now will need to have a (very recent) libv4l
to keep their setup working.

So I guess that the best way forward is to mark the driver as deprecated
now and remove it in say 2 releases?

Regards,

Hans

             reply	other threads:[~2009-06-17  6:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17  6:54 Hans de Goede [this message]
2009-06-17  8:33 ` How to handle v4l1 -> v4l2 driver transition 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=4A38931C.2060506@redhat.com \
    --to=hdegoede@redhat.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