> Hi, Hans,
>
>> perhaps 30% of the work done. My guess is that when ivtv-0.7/2.6.17 is
>> released some 70% of the work is done. The goal is to get it into the
>> kernel by 2.6.18.
>
> when (preliminary - May, July, August, autumn 2006) do you hope to get
> it into kernel 2.6.18 ?
Let's see: the window for major 2.6.17 patches closes after the weekend,
then say 1.5-2 months stabilization until 2.6.17 is released, then the two
week window opens for 2.6.18 and at that point ivtv should be added. It
will take another 1.5-2 months before 2.6.18 is officially released. So I
have two months to get it into the kernel, then another 2 months before it
is unleashed on the unsuspecting public.
Say in total 4 months? Give or take a few weeks. But people can start
testing in 2 months time with 2.6.18-rcX releases.
The official release is probably July/August.
That assumes I can get ivtv in for 2.6.18. It's very likely to go in, though.
Main problem is deciding on the API for ivtv-specific commands. They need
to be incorporated into the V4L2 spec. I also am less certain about
ivtv-fb, that might be delayed until 2.6.19. I hope not, but ivtv has a
higher priority if things get tight.
Hans
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
