On Tue, Mar 28, 2006 at 11:20:13AM +0200, Axel Thimm wrote: > 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).
Looks like all that was needed is to resurrect cx2341x.h. I'll be pushing out packages for v4l and ivtv for FC3, FC4 and FC5 in the testing repo of ATrpms. I hope these packages will make coexistance of ivtv devices and non-ivtv devices on older kernels possible and will also provide users with fresh drivers for newer hardware. > 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
pgp7jmGzOlfkf.pgp
Description: PGP signature
_______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
