On Wednesday 09 November 2005 20:01, Axel Thimm wrote: > On Wed, Nov 09, 2005 at 10:39:25AM -0500, Michael Krufky wrote: > > Axel Thimm wrote: > > >On Wed, Nov 09, 2005 at 08:43:01AM -0500, Michael Krufky wrote: > > >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. > > > > Please understand that we are merging the code into v4l cvs so that > > it will also be merged into the mainline kernel. > > I surely understand and appreciate this point! > > > 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. > > Exactly "the latest code" is not always what ivtv users want to > run. Placing the requirement of ivtv to work only on 2.6.15+ is quite > high IMHO. > > On Wed, Nov 09, 2005 at 04:11:04PM +0000, John Harvey wrote: > > So surely what we need then is a statement that as of 0.6 (or > > whatever it's called when it is released) ivtv is compatible with > > kernel 2.6.xx (15?) or requires this release of v4l2. > > Do we really want to cut 2.6 <= 2.6.15? Personally I would like to be > able to go as far back as 2.6.9. > > On Wed, Nov 09, 2005 at 07:00:06PM +0100, Hans Verkuil wrote: > > That's correct. It won't be released until either 2.6.15 is > > released and/or a stable v4l2 is released. The video4linux project > > makes regular releases, so we pick one that works and recommend > > that one to build against. > > Where is the latest release? The latest release I know of was 1 1/2 > years ago on April 2004. The versions in CVS are still the ones from > that date.
http://www.linuxtv.org/downloads/video4linux/ Latest is one month old. Are you still looking at the old bytesex.org site? > > > Remember: 0.4.x will remain for quite some time as the branch to > > use for kernels < 2.6.15 and where it is not possible (for whatever > > reason) to use v4l CVS or a stable snapshot. > > OK, can we agree on supporting 0.4.x for <N> time with backports like > new tuners etc.? At least with <N> overlaping the next release of > v4l? As far as I am concerned 0.4.x will remain actively supported (i.e. no functional difference between the 0.4 and 0.5/0.6) until the supporting drivers have become part of all the major distributions. After that I still want to provide support for simple things like new tuners. Of course, as the audio/video drivers in the kernel become more easily available it is less and less likely that large changes are backported (at least by me). It's a transition period with no doubt some problems, but after a year from now when hopefully the ivtv driver is a standard part of the major distributions it should be much easier for everyone. My (tentative) planning is to release 0.5.0 this weekend to start testing, after that I first have to try and solve the nasty bug where the mpeg stream seems to be shifted X bytes causing audio/video artifacts. Extremely annoying. Once that's done I want to backport (most of) the changes made for 0.5.0 to 0.4.1. So 0.4.1 should be in reasonable sync with 0.5.0. Hans _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
