On 06/28/12 15:09, the mail apparently from Ramakrishnan Muthukrishnan included:
Hi Sumit,
On Thursday 28 June 2012 11:41 AM, Sumit Semwal wrote:
On 27 June 2012 19:05, Martin Ertsåsmartiert@gmail.com wrote:
Yes, that is the start of it. Looks like everything is fine untill:
[ 2.258850] omapdss DPI: Could not find exact pixel clock. Requested 23500 kHz, got 23630 kHz [ 2.270050] omap_vout omap_vout: Buffer Size = 3686400 [ 2.277557] mmc1: queuing unknown CIS tuple 0x91 (3 bytes) [ 2.283538] omapdss OVERLAY error: check_overlay: paddr cannot be 0 [ 2.290252] omap_vout omap_vout: setup_overlay failed [ 2.295623] omap_vout omap_vout: apply_changes failed
And then stuff is failing, this is also something I always get.
This is actually fixed by the attached patch[1]; it was acked for 3.3+, but somehow got missed in the pull request.
Could you please use this and let us know if everything's ok for you?
Thanks.
The patch applied fine on tilt-3.4. When I bootup I get these messages:
[...] [ 3.180572] omap_vout omap_vout: 'hdmi' Display already enabled [ 3.186859] omap_vout omap_vout: 'hdmi' Display already enabled [ 3.193145] omap_vout omap_vout: Buffer Size = 3686400 [ 3.199645] omap_vout omap_vout: : registered and initialized video device 0 [ 3.207122] omap_vout omap_vout: Buffer Size = 3686400 [ 3.213562] omap_vout omap_vout: : registered and initialized video device 1 [...]
Now, if I do the following:
# gst-launch videotestsrc ! v4l2sink
I get a message:
[ 352.257080] omap_vout omap_vout: Unable to apply changes
and the gstreamer pipeline fails.
I will be glad to give you any other debug traces to fix the problem.
I think perhaps because I built all these v4l2 and vout pieces as modules, I get different behaviour. Maybe I am missing a driver needed or it doesn't work so well done as modules.
With Archit's patch Sumit kindly sent us (which is now on tilt-3.4) on inserting omap-vout.ko I got a NULL pointer OOPS: when I made the routine omap_vout_setup_video_data a bit more paranoid and give errors on NULL, the cause is that vout->vid_info.overlays[0]->manager is NULL.
[ 22.855377] Linux video capture interface: v2.00 [ 23.122558] omap_vout omap_vout: cannot find display [ 23.122589] omap_vout omap_vout: 'hdmi' Display already enabled [ 23.122589] omap_vout omap_vout: cannot find display [ 23.122589] omap_vout_setup_video_data: NULL manager for overlays[0] [ 23.148742] omap_vout: probe of omap_vout failed with error -12 [ 23.148895] omap_vout:Could not register Video driver
-Andy