On Tuesday, August 09, 2011 06:36:19 pm nitesh moundekar wrote: > I am worried about direction v4l2 is taking. It looks against the basic > principle of driver i.e. hardware abstraction.
There definitely should be an API which is hardware independent. However, the problem is that the hardware is so flexible that an hardware independent API needs to be necessarily enforce policies and possibly do complex image processing which is against the kernel philosophy and belongs to userspace. As I see it, it is necessary to provide more or less HW-dependent API to kernel V4L2. What we need is an userspace library abstracting that to simple HW-independent API. I think that libv4l is a very good way to do that, since it still provides the V4L2 interface but can do things in userspace. - Tuukka --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
