Okay. Thanks. I hope it works!

Btw, could you tell me which software you used to capture the camera. I guess the default camera app in android is not going to work unless we give some permissions. I have integrated gstreamer in android and when I tried running the pipeline,

gst-launch -v v4l2src ! surfaceflingersink

it gave me, ERROR: pipeline could not be constructed: no element "v4l2src". I guess there is some problem with gstreamer libraries and I will probably check with gstreamer guys.

Did you write your own camera interface program?

Thanks,
Krishnan.

On Wed, May 11, 2011 at 4:12 PM, Ash Charles <ash@gumstix.com> wrote:
I'm not guaranteeing anything but that sounds about right ;-).

I remember having to change permission on the /dev/video0 device node
to get it to work in Android too.
-ash

On Thu, May 12, 2011 at 1:03 AM, Saravanakrishnan
<krishnan.saravanak@gmail.com> wrote:
> Hi Ash,
>
> Thanks for the reply.. Yes. I figured that out. As, you had mentioned, I
> modified board-overo.c, added mt9v032 driver files and made changes in
> Kconfig and Makefile. Hence, the kernel got built successfully.  I just want
> to know whether the module gets built automatically. Will the camera be
> ready to use if I turn on the v4l, soc and i2c options in the kernel as
> specified in Kconfig? I don't have the board with me to test whether it is
> working or not. I will probably get in another 2 days.
>
> Thanks,
> Krishnan.
>
>
>
> On Wed, May 11, 2011 at 3:50 PM, Ash Charles <ash@gumstix.com> wrote:
>>
>> Hi Krishnan,
>>
>> The Android build is actually based off TI 2.6.32 kernel which should
>> already include the isp driver code required for the caspa sensor.
>> The only changes necessary should be adding the capsa i2c declaration
>> to the board-overo.c file and adding the mt0v32.c driver itself (along
>> with any necessary header/Kconfig changes).  Maybe there are some
>> changes in 2.6.34 causing the breakage?
>>
>> Prior to releasing Capsa, I actually tried out the sensor with an
>> Android build I had (making the fixes as above) and, once I tweaked
>> the permissions on /dev/video0, it actually came up just fine.
>>
>> -Ash
>>
>> On Tue, May 10, 2011 at 12:59 AM, Saravanakrishnan
>> <krishnan.saravanak@gmail.com> wrote:
>> > Hi,
>> >
>> > I am trying to interface CaspaVL to overo chestnut board (overo water)
>> > running android gingerbread with linux kernel 2.6.32.. I followed the
>> > wiki,
>> > http://wiki.gumstix.org/index.php?title=Caspa_camera_boards to patch the
>> > kernel. When I tried to build after patching, it throws up this error
>> >
>> > CC      arch/arm/mach-omap2/board-
>> > overo.o
>> >  LD      arch/arm/mach-omap2/built-in.o
>> >  LD      vmlinux.o
>> >  MODPOST vmlinux.o
>> >  GEN     .version
>> >  CHK     include/linux/compile.h
>> >  UPD     include/linux/compile.h
>> >  CC      init/version.o
>> >  LD      init/built-in.o
>> >  LD      .tmp_vmlinux1
>> > arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_xclk':
>> > /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:775:
>> > undefined reference to `isp_set_xclk'
>> > arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_power':
>> > /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:762:
>> > undefined reference to `isp_configure_interface'
>> > make: *** [.tmp_vmlinux1] Error 1
>> >
>> > The two functions are declared in isp.h and the include file is
>> > referenced
>> > in board-overo.c. I don't know why it is still showing this error. Am I
>> > missing something? Any help would be appreciated.
>> >
>> > Thanks,
>> > Krishnan.
>> >
>> > ------------------------------------------------------------------------------
>> > Achieve unprecedented app performance and reliability
>> > What every C/C++ and Fortran developer should know.
>> > Learn how Intel has extended the reach of its next-generation tools
>> > to help boost performance applications - inlcuding clusters.
>> > http://p.sf.net/sfu/intel-dev2devmay
>> > _______________________________________________
>> > gumstix-users mailing list
>> > gumstix-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
>> >
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> Achieve unprecedented app performance and reliability
>> What every C/C++ and Fortran developer should know.
>> Learn how Intel has extended the reach of its next-generation tools
>> to help boost performance applications - inlcuding clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users