Hi Bastian, On Thursday 28 October 2010 17:16:10 Bastian Hecht wrote: > > after reading the topic "controls, subdevs, and media framework" > (http://www.spinics.net/lists/linux-media/msg24474.html) I guess I > double-posted something here :S > But what I still don't understand is, how configuring the camera > works. You say that the subdevs (my camera sensor) are configured > directly. 2 things make me wonder. How gets the ISP informed about the > change The ISP doesn't need to know about sensor parameters except for image formats. Formats need to be set on both ends of every link, so the ISP will get informed when you will setup the sensor -> CCDC link. > and why don't I see my camera in the subdevs name list I posted. All subdevs > are from the ISP. See my answer to your previous e-mail for that. > My camera already receives a clock, the i2c connection works and my > oscilloscope shows that the sensor is throwing out data on the parallel bus > pins. But unfortunately I am a completely v4l2 newbie. I read through the > v4l2-docs now but the first example already didn't work because of the new > framework. Can you point me to a way to read /dev/video2? With the media-ctl and yavta test applications, just run ./media-ctl -r -l '"mt9t001 3-005d":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]' ./media-ctl -f '"mt9t001 3-005d":0[SGRBG10 1024x768], "OMAP3 ISP CCDC":1[SGRBG10 1024x768]' ./yavta -f SGRBG10 -s 1024x768 -n 4 --capture=4 --skip 3 -F $(./media-ctl -e "OMAP3 ISP CCDC output") Replace all occurences of 1024x768 by your sensor native resolution, and "mt9t001 3-005d" by the sensur subdev name. -- 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
