Em Mon, 15 Sep 2014 10:33:01 -0400 Nicolas Dufresne <nicolas.dufresne@xxxxxxxxxxxxx> escreveu: > > Le 2014-09-15 09:55, Mauro Carvalho Chehab a écrit : > > The DQBUF locking fixup was merged on libv4l2 for version 1.2. So, the > > potential breakage happens when libv4l2 is 1.2 and Gstreamer versions > > before 1.4. > > > > Do you have any procedure on gstreamer to fix a bug on stable releases? > A backport is possible, even though not trivial. Also, due to resources > there is no guaranty of a new stable 1.2 release. Well, if someone pops up with a problem with Gst 1.2 + libv4l 1.2 (with seems unlikely, as you pointed below), then we can provide them some directions to either: 1) revert the libv4l2 DQBUF patch; 2) upgrade to gst 1.4; 3) don't revert the POLLERR patch, if VBI is not needed on such specific scenario. > For GStreamer 0.10, it > is no longer maintained since 2 years already (mentioning since Laurent > was using an old vendor specific version base on this). Though this > situation isn't different from using a vendor specific kernel. Well, we can't do much with vendor-specific versions, especially when they rely on too old Kernels and/or too old Gstreamer versions. Anyway, I guess that the POLLERR patch were not backported to -stable. So, vendor-specific versions with old stacks won't be affected, as the POLLERR fixup was added on Kernel 3.16. I suspect that there aren't many places where a vendor distro using Gst 0.10 has Kernel 3.16. > > Those VBI applications don't have any, as they're not actively > > maintained anymore. Even if we patch them today, I guess it could take > > a long time for those changes to be propagated on distros. > > > > So, I guess that the best is to try to fix Gstreamer on the distros > > that are using libv4l version 1.2 and a pre-1.4 Gstreamer version. > This seems an unlikely mix, as Gst 1.4 was released at around the same > moment as libv4l2 1.2. Yes, I agree. Regards, Mauro -- 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
