On 6/29/06, Mauro Carvalho Chehab <[email protected]> wrote:
Also, on V4L side, the V4L1 api is stopping V4L development. V4L API 2
is already at kernel since the beginning of kernel 2.6 series, and fixes
several flaws at the old api (V4L1 API were designed on 2.1 series).
Still now, most applications still implement only V4L1, and people do
submit newer v4l1 drivers to us.
We do really go ahead, making V4L2 API the standard.
I don't think anyone would complain about dropping V4L1 if the people
pushing V4L2 were to port the 25 or so drivers that depend on V4L1 to
the V4L2 API. As long as those V4L1 dependent drivers are around
people are going to want to keep using V4L1. You may want to consider
building some in-kernel compatibility APIs into V4L2 to make porting
those drivers easier.
--
Jon Smirl
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
