On Mon, 16 Feb 2009, Hans Verkuil wrote: > >> If you want to add two bits with > >> mount information, feel free. But don't abuse them for pivot > >> information. > >> If you want that, then add another two bits for the rotation: > > > > Ok, this seems good. But if we want to distinguish between static sensor > > mount > > information, and dynamic sensor orientation changing due to pivotting, > > then I > > think we should only put the pivot flags in the buffer flags, and the > > static > > flags should be in the VIDIOC_QUERYCAP capabilities flag, what do you > > think of > > that? > > That's for driver global information. This type of information is > input-specific (e.g. input 1 might be from an S-Video input and does not > require v/hflip, and input 2 is from a sensor and does require v/hflip). > So struct v4l2_input seems a good place for it. A control could the return configuration of the current input. I don't see this as a new and novel use of controls. If V4L2_CID_VFLIP is set to 1, then the image is vertically flipped. What else would it mean? What does it mean now that's different? -- 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
