On Sunday 12 March 2006 19:51, Nicolas Mailhot wrote:
> Le dimanche 12 mars 2006 à 19:19 +0100, Hans Verkuil a écrit :
> > I have a life outside ivtv
> > you know. And, as I've said above, most of the effort is simply not
> > visible on the ivtv mailinglists. Just check the changelogs in the
> > 2.6.15 and 2.6.16 kernels to see what I've contributed there.
>
> Hans,
>
> Thank you for your answer. I came out a bit harsher than I intended.
>
> I know there is a steady ivtv -> v4l -> vanilla code flow
> I guess what I don't understand is why you don't release ivtv
> patchsets that work on a vanilla kernel (since as you wrote they do
> include your changes after a short merge time period)
>
> That would massively simplify the work of third-parties like me.
> Of course that would also mean stuff depending on v4l bits not merged
> yet wouldn't be available before the merge. But (and here maybe I'm
> wrong again) the v4l -> linus merge time does not seem the limiting
> factor right now.
The answer is really simple: I don't have the time. If someone else is
willing to make these patches, feel free. I want to concentrate my time
on fixing bugs, merging the driver into the kernel and adding new
features. Luckily people like Axel Thimm take care of making rpms for
various Fedora/RH releases. Most people seem to be able to work well
with the rpm or source tar.gz, and the last resort is always to use the
trunk version together with the latest v4l2 repository. It should work
with pretty much all kernels, but sometimes support for older kernels
is inadvertently broken, in which case it is usually quickly patched.
I'm happy to make kernel patches available for download on
ivtvdriver.org, but someone else will have to make them. It's as simple
as that.
Regards,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
