How to handle v4l1 -> v4l2 driver transition

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux