Hi Guennadi, On Thursday 02 February 2012 12:00:57 Guennadi Liakhovetski wrote: > On Thu, 2 Feb 2012, Laurent Pinchart wrote: > > Do all those sensors interleave the data in the same way ? This sounds > > quite hackish and vendor-specific to me, I'm not sure if we should try to > > generalize that. Maybe vendor-specific media bus format codes would be > > the way to go. I don't expect ISPs to understand the format, they will > > likely be configured in pass-through mode. Instead of adding explicit > > support for all those weird formats to all ISP drivers, it might make > > sense to add a "binary blob" media bus code to be used by the ISP. > > Yes, I agree, that those formats will be just forwarded as is by ISPs, but > the user-space wants to know the contents, so, it might be more useful to > provide information about specific components, even if their packing > layout cannot be defined in a generic way with offsets and sizes. Even > saying "you're getting formats YUYV and JPEG in vendor-specific packing > #N" might be more useful, than just "vendor-specific format #N". That's right. A single media bus code might not be the best option indeed. Vendor-specific blob codes (and 4CCs) then ? -- Regards, Laurent Pinchart -- 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
