Re: I wonder the difference with mbus_pixelcode and v4l2_colorspace.
Thanks Guennadi, Actually, I have been confused between MC MB. Including this, the link of Laurent is very helpful for me to make M5MOLS subdev driver. Regard, HeungJun Kim 2010-12-08 오후 4:23, Guennadi Liakhovetski 쓴 글: Hi On Wed, 8 Dec 2010, Kim, HeungJun wrote: Hi Guennadi, I wonder the difference with pixelcode mediabus and v4l2_colorspace. In mt9m001.c subdev driver, the format seems be determined using the combination pixelcode colorspace. In the previous kernel version(before using Media Controller), somtimes the pixelformat is used for defining format of isp device. But, I gonna change to use Media Controller. The change to mediabus pixelcodes has happened a while ago, whereas media controller is still not in the mainline. Mediabus is physically a bus between various parts of the media (video) subsystem, e.g., between a sensor and an SoC, or between resizers, format converters, etc., as long as data between them is exchanged directly over a set of data and sync lines, and not via mamory buffers. Original V4L2 fourcc codes on the other side describe data format in _memory_. The use of a pixelcode and a colorspace has been selected for the new mediabus API, so, that's what we have to use now in drivers, using this API. So, can you tell me where I find about Media Controller, especially pixelcode and colorspace? Again - these are not directly related things. The MC API has adopted, extended and is using the mediabus API, Laurent has documented many things wonderfully, have a look at http://www.ideasonboard.org/media/media/subdev.html#v4l2-mbus-format Thanks Guennadi --- 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
I wonder the difference with mbus_pixelcode and v4l2_colorspace.
Hi Guennadi, I wonder the difference with pixelcode mediabus and v4l2_colorspace. In mt9m001.c subdev driver, the format seems be determined using the combination pixelcode colorspace. In the previous kernel version(before using Media Controller), somtimes the pixelformat is used for defining format of isp device. But, I gonna change to use Media Controller. So, can you tell me where I find about Media Controller, especially pixelcode and colorspace? Thanks. Regards, HeungJun Kim -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I wonder the difference with mbus_pixelcode and v4l2_colorspace.
Hi On Wed, 8 Dec 2010, Kim, HeungJun wrote: Hi Guennadi, I wonder the difference with pixelcode mediabus and v4l2_colorspace. In mt9m001.c subdev driver, the format seems be determined using the combination pixelcode colorspace. In the previous kernel version(before using Media Controller), somtimes the pixelformat is used for defining format of isp device. But, I gonna change to use Media Controller. The change to mediabus pixelcodes has happened a while ago, whereas media controller is still not in the mainline. Mediabus is physically a bus between various parts of the media (video) subsystem, e.g., between a sensor and an SoC, or between resizers, format converters, etc., as long as data between them is exchanged directly over a set of data and sync lines, and not via mamory buffers. Original V4L2 fourcc codes on the other side describe data format in _memory_. The use of a pixelcode and a colorspace has been selected for the new mediabus API, so, that's what we have to use now in drivers, using this API. So, can you tell me where I find about Media Controller, especially pixelcode and colorspace? Again - these are not directly related things. The MC API has adopted, extended and is using the mediabus API, Laurent has documented many things wonderfully, have a look at http://www.ideasonboard.org/media/media/subdev.html#v4l2-mbus-format Thanks Guennadi --- 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: I wonder the difference with mbus_pixelcode and v4l2_colorspace.
On Wednesday, December 08, 2010 06:45:36 Kim, HeungJun wrote: Hi Guennadi, I wonder the difference with pixelcode mediabus and v4l2_colorspace. In mt9m001.c subdev driver, the format seems be determined using the combination pixelcode colorspace. In the previous kernel version(before using Media Controller), somtimes the pixelformat is used for defining format of isp device. But, I gonna change to use Media Controller. The pixelcode determines how to interpret the data flowing over the link. I.e. number of pins used, endianness, order of bytes within a sample. The colorspace determines how the pixel samples map to actual colors. There is some overlap between the two: YUV and RGB colorspaces also have their own pixelcodes. But two YUV (or two RGB) colorspaces will share the same pixelcode. In many devices there is only one colorspace possible for each pixelcode, so then it is just a matter of reading the documentation and filling in the correct value. More complex devices like HDMI receivers and transmitters often have a choice of colorspaces. Regards, Hans So, can you tell me where I find about Media Controller, especially pixelcode and colorspace? Thanks. Regards, HeungJun Kim -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Hans Verkuil - video4linux developer - sponsored by Cisco -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
