Hi, On Fri, Mar 25, 2011 at 1:34 PM, Patrick Radius <i...@notoyota.nl> wrote: > Ok, thanks! > However, I'm also quite curious about peoples thoughts about it from > here. > Since I think what's happing is quite OMAP specific. > For example, I was wondering where omap34xxcam.c gets it's memory it > should allocate from. > Is it the 'main' memory? Or does it share memory with a framebuffer > (overlay)? Or memory from the (M-4MO) sensor? > Is it possible I should allocate memory for it as boot argument? similar > like vmem=16M omapfb.vram=0:8M > > I can't find much information about this all...
You're using an old version of the driver. Please, use the newer one available in mainline. Regards, David Cohen > > On vr, 2011-03-25 at 13:24 +0200, Sakari Ailus wrote: >> Patrick Radius wrote: >> > Hi, >> >> Hi Patrick, >> >> I think this question will get better answered in the linux-media list. >> Cc it. >> >> > i'm trying to get camera support working on a relatively new Android >> > port to an OMAP 3430 based phone (Samsung GT-i8320 a.k.a. Samsung H1). >> > However calls to VIDIOC_REQBUFS fail with a -12 (OUT OF MEMORY). >> > As far as I can see this return error isn't even supposed to exist, >> > according to the V4L2 spec. >> > I'm using the code from Android on the Zoom2. >> > The sensor is a Fujitsu M-4MO. >> > >> > Any ideas on what could be wrong with the out of memory result? >> >> First of all, which version of the driver are you using, i.e. is it the >> current one going to upstream? >> > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
