I am running a modified fbdev_loopback on dvsdk_2_10_01_18 and have a long time ago modified one of the driver modules, specifically video_davinci_evm.c in the function image_sensor_hw_reset() with a last line added as "cpld_write(0x000000ff,0x00000010)" to swich off the LEDs on my evmdm365 board. Now busy implementing my status indication on the LED's I went and took this line out, rebuilt the kernel and then my application doesn't want to operate beyound the point where it calls fdCapture=open(CAPTURE_DEVICE, 0_RDWR | 0_NONBLOCK, 0). What I see at that point is it trying to do something in davinci_vpfe.c with vpfe_open() and the complaint being "nfs server x.y.z.s not responding, still trying".
It seems as if something in the filesystem is corrupted probably in /dev/video0 and I only get it going by copying my backed-up filesystem to ~/workdir/ and then it only works once as after a reset it can't open the device again. The makefile from the dvsdk_02_10_01_18 that is suppose to update my module drivers for irqk (which I have also added functionality to for gpio and ioctl stuff) does not update all of a sudden. I am not a linux guru so these things baffle me and it all started going wrong with me commenting out the line that was switching off the LEDs and rebuilding the uImage.
Any help would be appreciated and I could also give more info. Thanks, Jinh T.