Ronald Bultje wrote:
That's exactly what a kernel API should do. Using a userspace API to be able to change the kernel API without problems just moves the problem and still doesn't bring us anywhere.
What API should do, not neccessarily kernel API. Moving it to userspace allows to keep any bloat off the kernel (resulting in smaller, simpler and more stable kernel), the API can be more rich of features and can evolve to satisfy users requirements easier, than if it was whole in the kernel.
Besides, v4l2 does a pretty nice job, imho.
I agree. But why should there be the same kernel interface for say bt848 and an usb camera? The devices are completely different, they share only one thing - data they produce are interpreted as images, but thats not important from technical point of view :)
Sorry for my response latency. Marian
