Hi Laurent, On 03/24/2011 11:36 AM, Laurent Pinchart wrote: > Hi, > [snip] > > Padding at end of line can be configured through S_FMT. Other than that, all > other options (width, height, pixelcode) are fixed for a given mbus format > *for the ISP driver*. Other drivers might support different pixel codes for a > given mbus code (with different padding and/or endianness). > > Application either need to be aware of the media controller framework, in > which case they will know how to deal with mbus formats and pixel formats, or > need to be run after an external application takes care of pipeline > configuration. In the second case I suppose it's reasonable to assume that no > application will touch the pipeline while the pure V4L2 runs. In that case I > think your implementation of ENUM_FMT makes sense. > It is this second case which I am currently using, and why I submitted this patch. I think supporting ENUM_FMT in some form at /dev/videoX makes sense unless this second case is deemed obsolete and unsupported. But then that seems like a bigger break from V4L. -Michael MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler Registergericht: Amtsgericht Stuttgart, HRB 271090 Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner -- 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
