Axel Thimm wrote:
On Wed, Nov 09, 2005 at 08:43:01AM -0500, Michael Krufky wrote:
We are compatible with Vanilla 2.6.X kernels, through the use of #IF
KERNEL_VERSION and compat.h magic.... HOWEVER, some non-standard
kernels have backported newer features into older kernels, and our
tests based on KERNEL_VERSION fail in these cases. Because of this,
sometimes builds will fail on these non-standard kernels.
No, as pointed out on the v4l list, this has nothing to do with
non-standard kernels. We should keep the discussion about specific
bugs in v4l code on that list.
This is not true. What I've said about non-standard kernels is true.
However you are correct, we will keep that discussion on the v4l list.
What *is* relevant to ivtv is the dependency to the state of v4l
cvs. The current model w/o keeping copies of migrated drivers in ivtv
means that whenever v4l cvs is in a bad state like it currently is
users will not be able to get ivtv code running.
No offence to v4l code! Every code has to go through development and
its cvs/svn/etc developement area will be bleeding, same goes for
ivtv. But having this dependency means that ivtv would be able to
release a stable 0.6.x only if there will be a stable v4l release
containg the required modules, too. Or otherwise ivtv 0.6.x will build
on Mondays and fail on Tuesdays depending on the state of v4l cvs.
Hans, please reconsider keeping a copy in ivtv. Since you are
currently maintaining both copies they shouldn't diverge anyway. And
the default build could skip building them. I just want
users/packagers to have a workaround when things break. Just to give a
number, I usually roll out ivtv packages half an hour after they leave
svn. Today I've used all my day on hunting v4l bugs just to see if the
modules build.
Please understand that we are merging the code into v4l cvs so that it
will also be merged into the mainline kernel. Once the code is in
mainline, v4l cvs will not be needed if the user is running the latest
kernel version, unless there are further changes in v4l cvs needed that
are newer than what's in the latest kernel.
-Michael Krufky
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
