> >=20
> > bttv 0.8.x never worked with an unpatched 2.4.x kernel.
>
> It did work with v4l2 built as a stand-alone module.
Ok, with that hack (breaking all other v4l modules) it worked.
> v4l1
> compatibility did not work because of an undefined symbol but who
> cares about that? Anyone installing v4l2 and bttv 0.8.x wants v4l2
> and couldn't care less about v4l1. :-)
It doesn't matter for bttv anyway because bttv has both v4l and v4l2
fully implemented. The saa7134 driver is different, that one needs the
v4l1-compat module for v4l support.
> > 2.4.19-pre8
> > will be the first one where you can build bttv 0.8.x without additional
> > patches (if you are happy with v4l, for v4l2 support you still need v4l2
> > patches).
>
> Patches or just building the v4l2 module (outside the kernel tree)?
building v4l2 separate will work too (and _not_ break the binary
compatibility for other v4l drivers as the videodev module isn't touched
any more).
> At any rate, you must be saying that 2.4.19-pre8 will have the
> required "2.5 bits" that bttv 0.8.x needs backported to it?
Yes, videodev.c will be the same like 2.5.8 plus 2.4.x backward
compatibility.
Gerd
--
You can't please everybody. And usually if you _try_ to please
everybody, the end result is one big mess.
-- Linus Torvalds, 2002-04-20
_______________________________________________
Video4linux-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/video4linux-list
