DVSDK on OMAP/3530

I'm trying to run the DVSDK 3.01.00.03 on an OMAP/3530 board which is not the OMAP3EVM (close, but from a different manufacturer). I've ported my board specifics to the kernel that comes with the DVSDK and everything seems to work.

Except for the video demos :-( When I try to run 'decode', it attempts to open the device '/dev/video1' which I've deduced is a display in video mode. However, I can't figure out where or how that device is supposed to be created.

I've compared my kernel config with the standard EVM config and all of the VIDEO/DSS/FB options match.

Can someone give me some help/guidance?

note: I'm not sure the best place to ask this - the DVSDK getting started guide refers to [email protected] but I cannot find it...

Thanks

------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Hi,

On a board I'm working on, it has the OMAP 3530's camera port connected to the Davinci DM6467's VPIF port. The Davince is supposed to send BT656 stream over this link to OMAP. How to get the OMAP camera driver to work in this situation?

In kernel config, I set the CONFIG_VIDEO_OMAP3_CAM=yes option. I saw that omap34xxcam.c got compiled and the omap34xxcam device got probed during boot up. But I don't get a /dev/video0 node.

Do I need to write a specific driver for the Davinci VPIF interface? What else do I need to do?

Thanks,
Ke

[Hiremath, Vaibhav] Atleast from description I could see you are referring to TI PSP release, since camera driver is still accepted to main-line.

In that case, the PSP release does support BT656 interface, the only difference from your set-up is, we are getting BT656 stream from Video Decoder TVP5146 and you are getting it from DM6467.

The important points to look for -

- Interfacing: Since OMAP supports bridge lane shifter, where you can interface your 8 bit data likes to any of 0-15 camera datalines. The release configuration fro lane shifter is 2, that means the interfacing is from 2-11.

- OMAP35x works in slave mode, that means the synchronization is dependent on incoming pixel clock.

- Slave driver: You have to have slave driver for your interface. Please refer to tvp514x-int.c
http://arago-project.org/git/people/?p=sriram/ti-psp-omap.git;a=blob;f=drivers/media/video/tvp514x-int.c;h=aa2048b43b9d622c61a96551a8f20a1d75bf0a88;hb=da0c86a8f3bd57fad0ccd05eb1b5e3326d7f36aa

Hope this gives you some pointers.

Thanks,
Vaibhav

[Hiremath, Vaibhav] How are you making sure that DM6467 provides BT656 stream out on data pins.

[Hiremath, Vaibhav] I believe I had answered similar query from you earlier today, let me summarize it here again -

The V4L2 device nodes will get created under /dev/videox Where, x = 1 or 2 depending on CONFIG_FB_OMAP2_NUM_FBS.

The equation would be,

Num of V4l2 nodes = 3 - CONFIG_FB_OMAP2_NUM_FBS

And CONFIG_FB_OMAP2_NUM_FBS can not be less than 0.

Thanks,
Vaibhav