Hi Laurent, The first patch in the series fixes a warning, introduced by a recent framework change. Maybe you already have a similar one in your queue, drop this one then, please. Patch 2/3 implements support for asynchronous controls, using V4L2 events. Patch 3/3 adds a metadata device node to enable streaming of private payoad header to the user, based on your recent patch series. As everybody was agreeing, I didn't use patch 2 from the series, adding a new metadata video device type, using the GRABBER type instead. The additional video node is so added unconditionally in this patch, which I find superfluous and confusing for the user, because most cameras will not have any private data in the payload header, so, those nodes will be useless. I'm open to suggestions to make this node conditional on something - on a quirk flag? Unfortunately you can only find out, whether a camera has additional data in the header, when you receive the first frame. Thanks Guennadi -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
