On Monday 10 October 2005 16:44, Mauro Carvalho Chehab wrote:
> Hans,
>
> Em Dom, 2005-10-09 às 17:44 +0200, Hans Verkuil escreveu:
> > On Sunday 09 October 2005 17:27, Adam Forsyth wrote:
> > > It says right at the top of the the cvs info page that it often only
> > > works on the current -rc, and a patch is needed to make it work on the
> > > latest stable kernel. Is ther eany good reason compatibility isn't
> > > maintained?
> >
> > I get the feeling that backwards compatibility isn't a high priority.
>
> If you are talking about V4L, we have a period of two months without
> maintainer. During that period, we lost compatibility with 2.4. Also,
> some contributions were not tested with older versions. We did an effort
> to test backwards compat until 2.6.8.
> DVB is another history. They don't provide backward compatibility. In
> fact, their CVS is meant to compile on the latest -mm or -rc kernel
> version. We had to remove some DVB code from V4L three because of code
> conflicts caused by this. Also, DVB code on V4L is backward compatible
> with 2.6.12 and 2.6.13. With the merging scripts, we also provide
> compatibility with DVB development tree. We may provide backward compat
> with other DVB versions providing that somebody interested on it provide
> us patches for it.
Sorry Mauro, I quickly realized I was mistaken and that I formed the wrong
impression. My apologies for judging too quickly.
>
> > It isn't
> > helped by the crosslinks between the v4l and dvb repositories. And
> > they've just restructured their repository, so that may also contribute.
> > Anyway, I'm now looking at a way to keep a minimum subset with ivtv,
> > preferably with just the unchanged v4l sources so that all I have to do
> > is to copy them from v4l to ivtv.
>
> You may do it, if you wish. But it would be nice to keep duplicated
> codes "read-only" on ivtv. If you guys find a bug or want to send an
> improvement, please send to V4L mailing list for us to apply. Then, you
> may copy the newer version. This way, we will avoid having duplicated
> code, with different patchsets on it.
As you may have read my earlier posting I've reconsidered. All supporting
drivers are moved to v4l and during the transition period (at least until
these drivers turn up in distributions like Fedora Core) we keep maintaining
the stable 0.4 branch which still contains the copies of these drivers.
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
