Hi Gary,

On Thursday 01 September 2011 14:50:59 Gary Thomas wrote:
> On 2011-09-01 03:51, Enrico wrote:
> > On Wed, Aug 31, 2011 at 6:33 PM, Laurent Pinchart wrote:
> >> On
> >> http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp
> >> - omap3isp-next (sorry for not mentioning it), but the patch set was
> >> missing a patch. I've sent a v2.
> > 
> > Thanks Laurent, i can confirm it is a step forward. With your tree and
> > patches (and my tvp5150 patch) i made a step forward:
> > 
> > Setting up link 16:0 ->  5:0 [1]
> > Setting up link 5:1 ->  6:0 [1]
> > Setting up format UYVY 720x628 on pad tvp5150 2-005c/0
> > Format set: UYVY 720x628
> > Setting up format UYVY 720x628 on pad OMAP3 ISP CCDC/0
> > Format set: UYVY 720x628
> 
> I'm at nearly the same point, but I'm getting a couple of strange messages:
> # media-ctl -r -l '"tvp5150m1 2-005c":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP
> CCDC":1->"OMAP3 ISP CCDC output":0[1]' Resetting all links to inactive
> Setting up link 16:0 -> 5:0 [1]
> Setting up link 5:1 -> 6:0 [1]
> # media-ctl -f '"tvp5150m1 2-005c":0[UYVY 720x480], "OMAP3 ISP CCDC":0[UYVY
> 720x480], "OMAP3 ISP CCDC":1[UYVY 720x480]' Setting up format UYVY 720x480
> on pad tvp5150m1 2-005c/0
> Format set: unknown 720x480
> Setting up format unknown 720x480 on pad OMAP3 ISP CCDC/0
> Format set: unknown 720x480
> Setting up format UYVY 720x480 on pad OMAP3 ISP CCDC/0
> Format set: UYVY 720x480
> Setting up format UYVY 720x480 on pad OMAP3 ISP CCDC/1
> Format set: UYVY 720x480
> 
> # yavta -f UYVY -s 720x480 -n 6 --capture=6 -F /dev/video2
> Device /dev/video2 opened.
> Device `OMAP3 ISP CCDC output' on `media' is a video capture device.
> Video format set: UYVY (59565955) 720x480 buffer size 691200
> Video format: UYVY (59565955) 720x480 buffer size 691200
> 6 buffers requested.
> length: 691200 offset: 0
> Buffer 0 mapped at address 0x40211000.
> length: 691200 offset: 692224
> Buffer 1 mapped at address 0x402dc000.
> length: 691200 offset: 1384448
> Buffer 2 mapped at address 0x4047f000.
> length: 691200 offset: 2076672
> Buffer 3 mapped at address 0x40614000.
> length: 691200 offset: 2768896
> Buffer 4 mapped at address 0x40792000.
> Buffer 5 mapped at address 0x40854000.
> Unable to start streaming: 32.
> 
> What does 'Format set: unknown 720x480' mean from media-ctl?

That probably means that media-ctl got compiled against a different media 
controller API version than the one running on your system. Make sure you set 
the --with-kernel-headers= to the path to kernel headers for the kernel 
running on your system.

> Why 'Unable to start streaming: 32' - is this an EPIPE error?

That means the pipeline hasn't been configured properly. Either the pipeline 
is broken, or formats on two ends of a link don't match.

> > Now the problem is that i can't get a capture with yavta, it blocks on
> > the VIDIO_DQBUF ioctl. Probably something wrong in my patch.
> > 
> > I tried also to route it through the resizer but nothing changes.
> > 
> > Is it normal that --enum-formats returns this?
> > 
> > Device /dev/video2 opened.
> > Device `OMAP3 ISP CCDC output' on `media' is a video capture device.
> > - Available formats:
> > Video format:  (00000000) 0x0 buffer size 0

-- 
Regards,

Laurent Pinchart
--
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

Reply via email to