On Wed, 24 Aug 2005, Hans Verkuil wrote:

>Keep in mind that we want to get rid of these separately maintained
>modules anyway, so I would suggest to see if we cannot just copy the
>video4linux sources instead. The latest cvs versions have all the
>missing tuners in, so there is no reason left to keep our own version.
>
>I'm trying to do the same with tveeprom right now. So if you could do
>that with the tuner module and tda9887 then that would help a lot. Any
>improvements over the video4linux sources should go there, not here.
>That includes changes to make it compile for 2.4, BTW. I asked and
>although the 2.4 support is currently broken, they think it should be
>fixed.

2.4 support looks... problematic. I'm not set up for multiple build
trees, but I've wrangled the v4l tuner into ivtv with only a few changes
to headers. The only thing I can see obviously missing for 2.4 are the
MODULE_PARM entries.

Once I've got tda9887 in a similar shape, and assuming it still works on
my PVR-150, I'll post it somewhere where hopefully people who want 2.4
support can provide feedback.

BTW, do you have a link for the abovementioned video4linux-list 2.4
thread?  If the breakage is small I can certainly try to fix #defines
and Makefiles. Familiarity with kernel/v4l/i2c API changes is not my
forte, however.


Cheers,
Phil


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to