Hi Laurent, 2013/1/22 Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>: > On Tuesday 22 January 2013 13:48:40 Adriano Martins wrote: >> 2013/1/22 Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>: >> > On Tuesday 22 January 2013 09:31:58 Adriano Martins wrote: >> >> Hello Laurent and all. >> >> >> >> Can you explain me what means the message in yavta output: >> >> >> >> "Unable to start streaming: Broken pipe (32)." >> > >> > This means that the ISP hardware pipeline hasn't been properly configured. >> >> well, I already configured it before, with: >> >> media-ctl -V '"OMAP3 ISP CCDC":2 [UYVY 640x480], "OMAP3 ISP preview":1 >> [UYVY 640x480], "OMAP3 ISP resizer":1 [UYVY 640x480]' >> and >> media-ctl -r -l '"ov5640 3-003c":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP >> CCDC":2->"OMAP3 ISP preview":0[1], "OMAP3 ISP \ >> preview":1->"OMAP3 ISP resizer":0[1], "OMAP3 ISP resizer":1->"OMAP3 >> ISP resizer output":0[1]' >> Do you think it can be a hardware problem or wrong frame format from >> sensor? Or media-ctl commands is wrong. > > The ISP doesn't support YUV formats at its input. If you sensor generates UYVY > 640x480 you should capture video directly at the output of the CCDC. You will > need a recent version of the OMAP3 ISP driver (v3.6 or newer). > Ok, I will try change the sensor output format, if it is not possible, I will get the recent version of the OMAP3 ISP driver and try capture directly from CCDC output. >> > Unlike most V4L2 devices, the OMAP3 ISP requires userspace to configure >> > the hardware pipeline before starting the video stream. You can do so with >> > the media-ctl utility (available at >> > http://git.ideasonboard.org/media-ctl.git). Plenty of examples should be >> > available online. >> > >> >> I'm using omap3isp driver on DM3730 processor and a ov5640 sensor. I >> >> configured it as parallel mode, but I can't get data from /dev/video6 >> >> (OMAP3 ISP resizer output) Thanks Regards Adriano Martins -- 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
