Hi Brijesh,
What timing! I literally *just* finished compiling our board-specific
file after hacking in the patch for the DavinciEVM when your email
popped in. I just modprobed the vpfe_capture module, and am ecstatic to
find that vpfe_probe did get called and the devices created.
Many thanks for the input!
Ryan
________________________________
From: Jadav, Brijesh R [mailto:brijes...@ti.com]
Sent: Thursday, March 05, 2009 6:05 AM
To: Ryan Talbot; davinci-linux-open-source@linux.davincidsp.com
Subject: RE: VPFE
Hi Ryan,
For the device to be created in /dev, you will need a dummy
slave device. vpfe_probe must be called whether slave is available or
not. If this is not getting called, it means there is some vpfe's name
mismatch between name with which driver is registered as a platform
device and name present in the board specific file in
arch/arm/mach-davinci directory.
Thanks,
Brijesh Jadav
________________________________
From: davinci-linux-open-source-boun...@linux.davincidsp.com
[mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On
Behalf Of Ryan Talbot
Sent: Thursday, March 05, 2009 7:42 AM
To: davinci-linux-open-source@linux.davincidsp.com
Subject: VPFE
We've got a custom DM6446-based board which has a DM648 pumping
BT656 video directly into the DM6446's VPFE. We're trying to use V4L to
grab the video frames, but are running into some problems. We're using
2.6.28-rc6 with Murali Karicheri's patches applied, and while the
modules load successfully ("vpfe_capture: init successful"), we still
get the following trying to open /dev/video0:
"Can't open /dev/video0: no such device or address".
It is maybe worth noting that we have to create this device node
everytime we boot using mknod. 'cat /proc/devices' does list '81 0
video4linux', though.
I will admit I don't have a great grasp of how the V4L
architecture is supposed to work. We don't have any other hardware
involved other than the DaVinci VPFE, i.e. no decoder chips (they're all
upstream and handled by the DM648). I noticed vpfe_probe never gets
called when modprobing... seems like it should be. Do we need to create
some kind of dummy slave device to get things kicking?
Our board supplier gave us a C64P image that passes video
through from VPFE to VPBE, so the hardware itself is OK. I didn't think
the C64P even had direct access to the VPFE - I thought it relied on the
ARM/DSPLink for video frames - but I guess that shows the depths of my
ignorance.
Any pointers much appreciated, and a big thanks to Murali
Karicheri for his hard work on the patches.
Ryan Talbot
VTTI
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
