I have tried now with a newer kernel (3.14) and I can't even get an stream from /dev/video0. The file is always empty.
Here is the dmesg of it: http://pastebin.com/pm720UnR It is correctly identifying the device, however it cannot grab any bytes from the dd command as below: dd if=/dev/video0 of=ImageOut.raw bs=10065748 count=1 Any tips on how to investigate it further? 2014-10-29 18:13 GMT-02:00 Rafael Coutinho <rafael.couti...@phiinnovations.com>: > Ok, just to be sure, I have others capture boards like Silan SC8113, > that's only on newer kernels? If so I'll backport it. > > 2014-10-29 17:08 GMT-02:00 Mauro Carvalho Chehab <m.che...@samsung.com>: >> Em Wed, 29 Oct 2014 16:34:09 -0200 >> Rafael Coutinho <rafael.couti...@phiinnovations.com> escreveu: >> >>> Hi all, >>> >>> I'm having trouble to make an SAA7115 (Actually it's the generic >>> GM7113 version) video capture board to work on a beagle board running >>> Android (4.0.3). >>> For some reason I cannot capture any image, it always output a green image >>> file. >>> The kernel is Linux-3.2.0 >> >> Support for GM7113 were added only on a recent version. >> >> So, you need to get a newer driver. So, you'll need to either upgrade >> the Kernel, use either Linux backports or media-build to get a newer >> driver set or do the manual work of backporting saa7115 and the bridge >> driver changes for gm7113 for it to work. >> >> Regards, >> Mauro >> >>> >>> My current approach is the simplest I have found so far, to avoid any >>> issues with other sw layers. I'm forcing a 'dd' from the /dev/video >>> device. >>> >>> dd if=/dev/video0 of=ImageOut.raw bs=10065748 count=1 >>> >>> And then I open the raw image file converting it on an image editor. >>> >>> In my ubuntu PC (kernel 3.13.0) it works fine. however on the Beagle >>> Bone with android it fails to get an image. >>> >>> I have now tried with a Linux (angstron) on beagle bone with 3.8 >>> kernel and this time is even worse, the 'dd' command does not result >>> on any byte written on the output file. >>> >>> The v4l2-ctl works fine on the 3 environments. I can even set values >>> as standard, input etc... >>> >>> I have attached the dmesg of the environments here: >>> >>> * Android - dmesg http://pastebin.com/AFdB9N9c >>> >>> * Linux Angstron - dmesg http://pastebin.com/s3S3iCph >>> * Linux Angstron - lsmod http://pastebin.com/vh89TBKQ >>> >>> * Desktop PC - dmesg http://pastebin.com/HXzHwnUJ >>> >>> I have one restriction on the kernel of android due the HAL drivers >>> for BBB. So changing kernel is not a choice. >>> >>> Anyone could give me some tips on where to look for other issues or debug >>> it? >>> >>> Thanks in advance >>> > > > > -- > Regards, > Coutinho > www.phiinnovations.com -- Regards, Coutinho www.phiinnovations.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
