OMAP 3430 Camera/ISP out of memory error

Quoted 1 line · Patrick Radius

Hi,

Hi Patrick,

I think this question will get better answered in the linux-media list. Cc it.

Quoted 9 lines

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?

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...

Quoted 16 lines

Quoted 1 line · Patrick Radius

Hi,

Hi Patrick,

I think this question will get better answered in the linux-media list. Cc it.

Quoted 8 lines

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.

Quoted 5 lines

Quoted 1 line

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hi,

Quoted 11 lines · Patrick Radius

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

Quoted 1 line

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

Quoted 30 lines · Sakari Ailus

Quoted 16 lines

Quoted 1 line · Patrick Radius

Hi,

Hi Patrick,

I think this question will get better answered in the linux-media list. Cc it.

Quoted 8 lines

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.

Quoted 5 lines

Quoted 1 line

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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Thanks,

I'm looking at
http://gitorious.org/linux-omap/mainline/trees/master/drivers/media/video

however, I can't seem to find the drivers I need.
I only see omap24xxcam while I was using the omap34xxcam from Linux kernel 2.6.32.9.
And I also don't see any M-4MO driver anymore.
I'm probably looking at the wrong spot, but...

As you can tell, I'm fairly new with OMAP programming.

Thanks!

Regards,
Patrick

Quoted 53 lines · David Cohen

Hi,

Quoted 11 lines · Patrick Radius

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

Quoted 1 line

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

Quoted 30 lines · Sakari Ailus

Quoted 16 lines

Quoted 1 line · Patrick Radius

Hi,

Hi Patrick,

I think this question will get better answered in the linux-media list. Cc it.

Quoted 8 lines

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.

Quoted 5 lines

Quoted 1 line

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Quoted 10 lines

Thanks,

I'm looking at
http://gitorious.org/linux-omap/mainline/trees/master/drivers/media/video

however, I can't seem to find the drivers I need.
I only see omap24xxcam while I was using the omap34xxcam from Linux kernel 2.6.32.9.
And I also don't see any M-4MO driver anymore.
I'm probably looking at the wrong spot, but...

You need to get an up-to-date mainline kernel. The driver is in the
directory: drivers/media/video/omap3isp/
I don't recommend you to use 2.6.32, as it depends on some new V4L2 stuff which you won't natively find in such old kernel version. I also suggest you to CC [email protected] as well in next questions.

Br,

David

Quoted 65 lines

As you can tell, I'm fairly new with OMAP programming.

Thanks!

Regards,
Patrick

Quoted 53 lines · David Cohen

Hi,

Quoted 11 lines · Patrick Radius

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

Quoted 1 line

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

Quoted 30 lines · Sakari Ailus

Quoted 16 lines

Quoted 1 line · Patrick Radius

Hi,

Hi Patrick,

I think this question will get better answered in the linux-media list. Cc it.

Quoted 8 lines

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.

Quoted 5 lines

Quoted 1 line

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html