> > v4l has been _the_ interface for years. And it probably takes at least
> > one more year until v4l2 shows up in a stable kernel (2.6). I don't
> > think we can phase out v4l1 ...
>
> Yes, it has been _the_ interface for years, but it still remains
> hopelessly incomplete and poorly defined.
Neverless lots of applications use it, and that's why we have to keep
it. The kernel still has a.out support ...
> It will hopefully go the same way as i2c-old,
i2c-old is something else. It's internal to the kernel. Whenever
a driver uses the old or new i2c code makes no difference for the
API which the applications will see.
Gerd
_______________________________________________
Video4linux-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/video4linux-list