Hi, I started creating v4l packages from v4l's tip. I guess the only ivtv version that makes sense to use against this is the trunk (0.7).
Also, what's the safest & cleanest way to divert reading #include <linux/....h> to first check /usr/include/v4l (where I'll deposit the v4l's headers from the tip) and then the kernel sources? The grand plan is to have v4l and ivtv packages built in a compatible (e.g. layered) way for several distributions. v4l currently supports builds at least as far back as 2.6.12, and probably ivtv 0.7 will then build on these v4l enhanched kernels, too (unless there are other requirements on ivtv 0.7). What I'd really love to see is 2.6.9 supported by both v4l and ivtv trunks/tips to allow setting up mythboxes based on RHEL & clones base systems. -- Axel.Thimm at ATrpms.net
pgp2aglGnBIfz.pgp
Description: PGP signature
_______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
