Hi Sylwester On Tue, 31 Jan 2012, Sylwester Nawrocki wrote: > Hi all, > > Some camera sensors generate data formats that cannot be described using > current convention of the media bus pixel code naming. > For instance, interleaved JPEG data and raw VYUY. Moreover interleaving > is rather vendor specific, IOW I imagine there might be many ways of how > the interleaving algorithm is designed. > > I'm wondering how to handle this. For sure such an image format will need > a new vendor-specific fourcc. Should we have also vendor specific media bus code ? > > I would like to avoid vendor specific media bus codes as much as possible. > For instance defining something like > > V4L2_MBUS_FMT_VYUY_JPEG_1X8 Hmm... Are such sensors not sending this data over something like CSI-2 with different channel IDs? In which case we just deal with two formats cleanly. Otherwise - I'm a bit sceptical about defining a new format for each pair of existing codes. Maybe we should rather try to describe individual formats and the way they are interleaved? In any case the end user will want them separately, right? So, at some point they will want to know what are those two formats, that the camera has sent. No, I don't know yet how to describe this, proposals are welcome;-) > for interleaved VYUY and JPEG data might do, except it doesn't tell anything > about how the data is interleaved. > > So maybe we could add some code describing interleaving (xxxx) > > V4L2_MBUS_FMT_xxxx_VYUY_JPEG_1X8 > > or just the sensor name instead ? As I said above, I would describe formats separately and the way, how they are interleaved. BTW, this might be related to recent patches from Laurent, introducing data layout in RAM and fixing bytesperline and sizeimage calculations. Thanks Guennadi > Thoughts ? > > > Regards, > -- > Sylwester Nawrocki > Samsung Poland R&D Center --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/ -- 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
