Hi Hans, I understand. I will get in touch with the maintainer to see how we can fix this issue. Thank you so much for the help, Isaac On Sun, Jul 27, 2014 at 1:30 PM, Hans Verkuil <hverkuil@xxxxxxxxx> wrote: > On 07/27/2014 10:42 AM, Isaac Nickaein wrote: >> On Sun, Jul 27, 2014 at 12:56 PM, Hans Verkuil <hverkuil@xxxxxxxxx> wrote: >>> No. Whoever maintains that repository applied v4l code from some newer >>> kernel without apparently ever testing it. This is really the responsibility >>> of maintainer of that repository and is out of our control. >>> >>> You need to address your questions to that repository maintainer, we can't >>> help, I'm afraid. >>> >> >> Ah I see. I have some issues with v4l2 on this kernel version and I am >> trying to upgrade v4l2 to fix that. >> >> One last question: Can I remove current v4l codes in kernel, replace >> them with the V4L2 backport (provided by linuxtv), fix the >> compatibility issues (hopefully) to get a kernel source with newer >> v4l2 code? >> >> I am not sure if the v4l2 backport is the same type of code that is >> present in kernel source at "drivers/media/video", >> "drivers/media/dvb", etc. > > Yes, you can, but it isn't easy. > > In this repo: > > http://git.linuxtv.org/cgit.cgi/hverkuil/cisco_build.git/tree/?h=cobalt-mainline > > there is a patch-kernel.sh script that can patch a vendor kernel with the v4l > code from a fairly recent stable kernel (I think it is good for 3.14, I don't > know if it can backport from a 3.15 kernel). > > You need to set the target, orig_source and source paths correctly and then > run it. > > You end up with a huge patch that you can apply to your kernel. > > It's probably still not enough since you may have to add compat code from > v4l/compat.h to the drivers you want to compile in. It depends on what > drivers you want to compile how much work that is. > > I'm not going to give support for this, so you're on your own. The repo > owner really should fix his tree. > > 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
