On Thursday 30 March 2006 02:45, Axel Thimm wrote:
> 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.
Why is that needed? I don't understand it. BTW, you may want to wait
with releasing anything until next week. The 2.6.17 kernel windows
closes after the weekend and v4l-dvb is still being changed a lot at
the moment.
Also, once the window is closed I'll turn ivtv-0.7 into a branch and
continue trunk development as 0.8. I'll also make a v4l-dvb-ivtv-0.7
repository which is supposed to be a stable v4l-dvb repo for ivtv-0.7.
It's experimentation only to see how well that works.
I expect that ivtv-0.8 will not be released but instead will be included
in the kernel pending unforseen circumstances.
> 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.
If you can make patches for 2.6.9 then I can add them to v4l-dvb.
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
