From: Patrick Radius <info@notoyota.nl>
To: linux-omap@vger.kernel.org
Subject: Re: OMAP 3430 Camera/ISP out of memory error
Date: Fri, 25 Mar 2011 12:34:53 +0100 [thread overview]
Message-ID: <1301052893.25083.3.camel@kaas> (raw)
In-Reply-To: <4D8C7B62.9010701@maxwell.research.nokia.com>
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...
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?
>
next prev parent reply other threads:[~2011-03-25 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 10:52 OMAP 3430 Camera/ISP out of memory error Patrick Radius
[not found] ` <4D8C7B62.9010701@maxwell.research.nokia.com>
2011-03-25 11:34 ` Patrick Radius [this message]
2011-03-25 14:34 ` David Cohen
2011-03-25 19:01 ` Patrick Radius
2011-03-26 13:16 ` David Cohen
2011-03-26 13:32 ` Patrick Radius
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1301052893.25083.3.camel@kaas \
--to=info@notoyota.nl \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).