ivtv 0.7.0 compiles on 2.6.18 kernel, but I can't test that. Anyway, that's the ebuild:
No. Every kernel version requires a new ivtv version. This has been the case for nearly every single kernel. ivtv 0.8.0 will be for the 2.6.18 kernel.
http://www.ivtvdriver.org <- read it.
Uhm, I don't see that 0.7.0 won't work on 2.6.18. I only read "ONLY for 2.6.17", yes, but that was written when 2.6.18 wasn't released yet. So, my question is if there's someone that could try that ebuild.
No. Every single ivtv to date is specialized per kernel. If you'd follow the link I sent you, you'd come to IVTV's website. Where if you looked at their development process you'd see that they're hammering out kinks with ivtv-0.8 for 2.6.18. Soon after that you will see a ivtv-0.9 branch for 2.6.19.
dude, open your mind ;)
I don't see anything releated to your sentence and here, "modprobe ivtv" on 2.6.18 works perfectly.
I'd prefer to keep this open to who can test ivtv 0.7.0 on 2.6.18.
Yes. Read the change log. Notice how the 0.8 series has to make changes to support all of the V4L2 interfaces. The point since V4L1 support has started to be stripped out in 2.6.18, then support for all the features and hooks of ivtv won't be accessible unless you use ivtv-0.8.
(In reply to comment #5)
> dude, open your mind ;)
> I don't see anything releated to your sentence and here, "modprobe ivtv" on
> 2.6.18 works perfectly.
> I'd prefer to keep this open to who can test ivtv 0.7.0 on 2.6.18.
As Cardoe already noted; the 0.7.0 version is designed for 2.6.17 kernels. Upstream says that 0.8.0 will work with 2.6.18 (just as they always release for new kernel versions). Just because it may work on your machine (although you noted earlier "ivtv 0.7.0 compiles on 2.6.18 kernel, but I can't test that" so I wonder a bit) doesn't mean we will go against upstream's release policy.
Wait for the 0.8.0 version.
Fabio: Now there is a 0.8 version. It will be going into Portage shortly.
ok, great, sorry for all the buzz.