From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Adriano Martins <adrianomatosmartins@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: yavta - Broken pipe
Date: Wed, 23 Jan 2013 00:29:01 +0100 [thread overview]
Message-ID: <2582320.50e9nd63SM@avalon> (raw)
In-Reply-To: <CAJRKTVphZiZyUTzmxaG_rU0Ba_08jRZAqADeFQNdQR+pZX1YQg@mail.gmail.com>
Hi Adriano,
On Tuesday 22 January 2013 13:48:40 Adriano Martins wrote:
> 2013/1/22 Laurent Pinchart <laurent.pinchart@ideasonboard.com>:
> > 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).
> > 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)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-01-22 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJRKTVqnB6-8itbr3Cu-jnJo-zz3dYQeJ98sLnD-Eo9hvNS5iQ@mail.gmail.com>
2013-01-22 15:31 ` yavta - Broken pipe Laurent Pinchart
2013-01-22 15:48 ` Adriano Martins
2013-01-22 23:29 ` Laurent Pinchart [this message]
2013-01-23 11:05 ` Adriano Martins
2013-01-22 11:39 Adriano Martins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2582320.50e9nd63SM@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=adrianomatosmartins@gmail.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox