On Sun, Jul 22, 2007 at 01:44:15PM +0200, Hans Verkuil wrote: > On Sunday 22 July 2007 13:20:19 Axel Thimm wrote: > > Hi, > > > > On Thu, Jul 12, 2007 at 08:05:19AM +0200, Hans Verkuil wrote: > > > Try the latest code from the subversion trunk > > > (http://ivtvdriver.org/viewcvs/ivtv/trunk.tar.gz?view=tar). I've > > > removed the ivtv driver itself from that code so it only contains > > > the utilities, ivtv-fb and the saa717x module. This should be used > > > for 2.6.22 and up. > > > > Which is the authoritative driver code (in development, not the > > in-kernel) now, v4l-dvb? > > The authoritative ivtv driver code is v4l-dvb. For ivtv-fb and the > saa717x module (for Japanese cards) it is still the svn ivtv trunk > repository. I thought about keeping it in svn trunk as well, but I'm > happy with the way v4l-dvb works and Mauro (the v4l-dvb lead) merges my > changes pretty quickly. So rather then having to keep two trees in sync > I decided to develop in v4l-dvb. > > I hope to get ivtv-fb into 2.6.23 (no guarantees) and in that case > ivtv-fb will also be moved to v4l-dvb. > > A tree including ivtv-fb is already available here: > > http://www.linuxtv.org/hg/~hverkuil/ivtv-fb > > Note that for kernels >= 2.6.18 and <= 2.6.21 the ivtv-0.10 branch will > still be maintained for a substantial amount of time.
And ivtv-1.0.x will be supporting kernel >= 2.6.22? E.g. when several fixes make it into ivtv-1.0.x, but only appear at say 2.6.25, would we be able to build the module for 2.6.22 still? Thanks! -- Axel.Thimm at ATrpms.net
pgpGh9ZB0wn2j.pgp
Description: PGP signature
_______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
