1. the latest and greatest ivtv is 0.5.x svn trunk
2. a week ago it still depended on some v4l cvs changes not merged
upstream (ie could not build without a private v4l tree dump)
3. and it had firmware loading problems with the latest 2.6.15-rc git
dumps
4. the merging process stalled considerably when the paken fork was
discovered
The root of the problem of course is ivtv developpers still haven't
understood the "release early, release often" part and are aiming for
a perfect (cleaned-up and feature-complete) driver before submitting
it. Instead of merging everything now (experimental) and finishing the
paken merge cleanup / inside the kernel.
ivtv 0.5 is not even available as a kernel patchset, so you get the
idea. ivtv writers would get a boatload of feedback if it behaved like
any other kernel patchset.
Now don't get me wrong, the ivtv people did and are doing a wonderful
job driver-side, but they seriously need to learn to integrate in the
kernel ecosystem. Someone wrote in the thread about the need to "kick"
them a bit to make them understand this. I'm afraid this feeling is
shared by a lot of other people. The low priority given to merging is
real frustrating.
Regards,
--
Nicolas Mailhot
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
