I am trying to understand, at least in general detail how media
framework, omap3 isp and v4l2 cooperate to control camera in newer
kernels, I am using caspa camera. As it is written, to configure
pipeline we must use media-ctl, in every tutorial there are those
media-ctl -v -l '"mt9v032 3-005c":0->"OMAP3 ISP CCDC":0'
media-ctl -v -l '"OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC
media-ctl -v -f '"mt9v032 3-005c":0 [SGRBG10 752x480]'
media-ctl -v -f '"OMAP3 ISP CCDC":1 [SGRBG10 752x480]'
as I understand we are connecting some end-points in the pipeline.
In this case the camera driver output goes to oma3isp ccdc and it
pushes this data to omap3isp output.
Firstly, I am wondering what ccdc stands for, is it charged-couple
device control? Or does this mean something completely different.
Also, on older kernels you could get some snaps with mplayer, like
it is explained here:
it says that for capturing images I could use "
compatible capture app (mplayer w/v4l2 plugin, Laurent's yavta app,
etc.)". I can get raw images with yavta, but is it possible
to get something like bmp or jpeg using mplayer? The command from
the link about caspa camera boards for 2.6.34 doesn't work in newer