From: Steve S. <sa...@gm...> - 2011-09-30 18:07:15
|
On Fri, Sep 30, 2011 at 10:36 AM, Thots <sra...@as...> wrote: > > I finally finished installing media-ctl. I had to get past a few different > "autoreconf --install" and "./configure" errors. I forget exactly how I got > past the config.guess problem. I think I just copied the file to a > different location. > > One problem I had to get past was figuring out what to use for the > "--with-kernel-headers" parameter when running ./configure. It turns out > first I needed to run "make ARCH=arm headers_install" from my linux kernel > folder. Then I needed to move the resulting folder onto my gumstix. This > is the location "--with-kernel-headers" should be set to. > > After installing media-ctl, I was able to run yavta. It ran properly, but > it saves the pictures it takes in a .bin file. I haven't yet been able to > verify the images look correct. I too have been attempting to get the Caspa working with Linux 3.0. I have the Caspa support integrated into the kernel now (the 2 most recent commits): http://www.sakoman.com/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=shortlog;h=refs/heads/omap-3.0-pm The defconfig I used to build the kernel is in my OE repo: http://www.sakoman.com/cgi-bin/gitweb.cgi?p=openembedded.git;a=blob;f=recipes/linux/linux-sakoman-pm-3.0/omap3-multi/defconfig;h=4f2c9f7d0830ef4030043248db3f881ceed0570b;hb=f06b8114a82705362c0fb89af97ff9e8286b4080 And my latest GNOME image binary has the above kernel as well as the media-ctl and yavta utilities for testing: http://sakoman.com/category/8-gnome-daily-builds-r13.html Things look good until I try to capture something, then the system locks up :-( I used the same commands that you describe below. Were you using a 3.0 kernel or 2.6.39? I guess the other difference is that I cross compiled the media-ctl and yavta apps. Time to debug I guess :-( Regards, Steve > Here are the commands I used for media-ctl and yavta: > (This first command just displays media-ctl information and can be skipped) > media-ctl -p > > media-ctl -r -l '"mt9v032 3-005c":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP > CCDC":1->"OMAP3 ISP CCDC output":0[1]' > > media-ctl -f '"mt9v032 3-005c":0[SGRBG10 752x480 (2,10)/752x480], "OMAP3 ISP > CCDC":1[SGRBG10 752x480]' > > ./yavta -p -f SGRBG10 -s 752x480 -n 4 --capture=10 --skip 9 -F `media-ctl -e > "OMAP3 ISP CCDC output"` > > Right now, my main goal is to is to get the Caspa camera and MT9V032 sensor > recognized by Linux programs like Cheese. For example, after following all > the instructions on the gumstix wiki for patching the 2.6.34 kernel to work > with the caspa camera, Cheese would automatically recognize the camera and > start displaying video. > > http://wiki.gumstix.org/index.php?title=Caspa_camera_boards > > Here is part of an e-mail I received from the very smart Laurent Pinchart > who's done a lot of hard work on the Linux ISP code: > > -me > > Also, I'm really wondering how I am going to get other Linux > > applications to use the Caspa camera with the MT9V032 sensor. I > > remember that a while ago there was a modified gumstix Linux kernel > > (2.6.34 maybe) that worked with the MT9V032 sensor and Caspa camera. > > When Linux applications like Cheese were turned on, they would > > automatically recognize the camera and start displaying the video. > > What do I need to do to make the Caspa camera automatically detected > > by programs like Cheese? > > -Laurent > "You will need to configure the pipeline first, and the run a V4L2 > application to capture video. As applications usually can't handle Bayer > formats properly, you will need to include the preview engine and > resizer in the pipeline to get YUV at the output of the pipeline, and > capture from the resizer output video node. > > A libv4l plugin for the OMAP3 ISP is planned, but no work has been done > it. It will let applications using libv4l use the OMAP3 ISP > transparently." > > > I'm guessing this work must have been done for the 2.6.34 kernel in the > MT9V032 patch since this patch allowed Cheese to automatically recognize the > camera. > http://cumulus.gumstix.org/sources/mt9v032-2.6.34.patch > > Does anyone know if we can use part of this patch for getting Linux > applications to automatically recognize the Caspa camera? If so, what part? > Or perhaps is there a better way to go about this than using the patch at > all? > > Getting Linux applications like Cheese to recognize the Caspa camera would > be great. > > > > JamesAng wrote: >> >> Hi Thots, >> >> Same goes to you on your success to get the device registered. (^^) >> >> A correction is that I only get it to work with linux-omap-2.6.39 kernel >> instead of steven's linux-omap3-2.6.39 nor 3.0 kernel. >> >> For media-ctl, I couldn't get it to compile on my Overo natively and I >> ended up doing it via cross-compilation using bitbake as per Scott's page. >> >> Because of this reliance on bitbake downloading the proper toolchain onto >> overotmp folder, I couldn't process with doing so for Steve's 3.0-pm >> kernel which I planned as he is using "angstrom-2010" instead of >> "angstrom-2008", >> >> Bitbake refused to process without a fresh working folder for the new >> version of toolchain used.. >> >> Tough luck with Kernel.org down for over 2wks.. >> >> James. >> >> > > -- > View this message in context: http://old.nabble.com/Caspa-Camera-on-2.6.39-Kernel-tp32435194p32570553.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |