On Wed, 4 Mar 2009, ribrishimov wrote: > I am planning to export the chip identification information > to user space using VIDIOC_DBG_G_CHIP_IDENT. > Here's a sketch: > #define V4L2_IDENT_SMIA_BASE (0x53 << 24) > then in sensor driver's VIDIOC_DBG_G_CHIP_IDENT ioctl handler: > struct v4l2_dbg_chip_ident id; > id.ident = V4L2_IDENT_SMIA_BASE | (manufacturer_id << 16) | model_id; > id.revision = revision_number; > > Do you think this is acceptable? This is only meant for debugging and shouldn't be used by normal software. > Alternatively, VIDIOC_QUERYCAP could be used to identify the sensor. > Would it make more sense if it would return something like > capability.card: `omap3/smia-sensor-12-1234-5678//' > where 12 would be manufacturer_id, 1234 model_id, and > 5678 revision_number? You could always try to decode the manufacturer name and maybe even the model name. After all, pretty much every other driver does this. -- 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
