On Thu, 5 Mar 2009, Hans Verkuil wrote: > > ENUMINPUT is probably a better solution: you can say something like > "Camera 1 (sensor1)", "Camera 2 (sensor2)". > > It remains a bit of a hack, though. Maybe use some of the reserved bits in v4l2_input to show not only the sensor orientation, but also manufacturer, model, and revision? I wonder if there are enough bits for that? How does this discussion go? I point out that using reserved bits is not sustainable, does not allow enumeration of supplied properties, and provides no meta-data for the self-documentation of those properties. The control interface provides all these things. Then you point out that these aren't "controls" and say end of discussion. Though if one had considered allowing the control api to be used to provide sensor properties, then the solution to this problem would now be quite simple and obvious. -- 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
