Re: RFC: Drop V4L1 support in V4L2 drivers

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

 



Keeping v4l1 because some guys are still using some ancient setup is
not a good reason.  Keeping v4l1 because some app devs still haven't
bothered to update their apps is not a good reason, especially given
the amount of time they've had to complete this task.  Keeping v4l1
because package maintainers haven't bothered to update their packages
is not a good reason.

To put it simply, v4l1 is just dragging along dead weight.  It has
been replaced by something better and there's no reasonable excuse to
keep dragging it along.  There will always be someone complaining
because there will always be someone neglecting to make the transition
until the last possible second or resisting change even when it's for
the better.

App devs that haven't bothered to update -- you've had plenty of time
to get it done.  If you app breaks, it's not v4l's fault at this
point.

Users still on ancient hardware -- consider updating to cheap newer
alternatives but don't expect v4l to be held back because you refuse
to move forward.  Or politely request old drivers be converted.

Package maintainers -- if it's too much of a hassle to keep your
package(s) updated, consider giving that responsibility to someone
else.

The points made in this thread make it pretty obvious that dumping
v4l1 altogether is easily for the best and has only very minimal
negative impact.  And the negatives aren't anything that can't be
resolved completely with a little commitment to do so.

Best regards,
Derek
--
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