On Tuesday 11 July 2006 20:08, Stefan Wrobel wrote:
> I recall reading a long time back that 2.6.18 was the target kernel
> for merging in ivtv. I just read the changelog for 2.6.18-rc1 and
> didn't find anything relating to its inclusion in there. Is this
> still planned, or is ivtv never making it into the kernel? If not,
> what's holding it back? Thanks,
It's still in progress. It turns out to be a much larger job than I
anticipated. If you'll look closely at the changelog you'll see lots of
changes that I made to prepare for ivtv. In particular the
ivtv-specific MPEG API was replaced by a new v4l2 API. This in itself
was a time consuming task.
Next job will be to make a v4l2 API for MPEG decoding and (possibly)
frame buffer.
Current goal is to get it in 2.6.19 or 2.6.20. There's only so much time
I can spend on this, and API discussions take a lot of time. Also, as
I'm no expert on the decoding API I want to work on that by creating a
simple test application that I can use to see what works and what not.
Bottom line: the ivtv driver is BIG.
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
