All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Richard Cochran <richardcochran@gmail.com>,
	 Carlos Rafael Giani <dv@pseudoterminal.org>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: imx6: webkit html5 video with hardware acceleration
Date: Wed, 24 Sep 2014 09:42:37 -0700	[thread overview]
Message-ID: <5422F47D.1070009@boundarydevices.com> (raw)
In-Reply-To: <20140924045023.GB4588@netboy>

Hi Richard,

On 09/23/2014 09:50 PM, Richard Cochran wrote:
> On Tue, Sep 23, 2014 at 10:46:42PM +0200, Carlos Rafael Giani wrote:
>> Merely starting Chromium triggers the OOM killer already?
> 
> Yup.
> 
>> How much RAM does your board have?
> 
> 256 MB.
> 
>> And how much *free* RAM was
>> available when you started Chromium?
> 
> The Freescale kernel hackery is really hurting us. With the kernel in
> the alpha/beta branch, we need 144 MB for CMA. I am sure this is due
> to something dumb in the thousands of new FSL kernel patches, but I
> haven't had the time to track this down.
> 
> The daisy kernel worked on that board (with full screen video) with a
> CMA of 64 MB, but unfortunately the newer user space does *not* work
> with the daisy kernel. Brilliant stuff, that.
> 

You can tweak this through a kernel parameter:

	root@nitrogen:~# cat /sys/module/galcore/parameters/contiguousSize
	134217728

So if you add "galcore.contiguousSize=64M" to the kernel command-line,
you should get the old default.



  reply	other threads:[~2014-09-24 16:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 18:13 imx6: webkit html5 video with hardware acceleration Richard Cochran
2014-09-23 18:33 ` Gerard Bucas
2014-09-23 18:55   ` Bin Lin
2014-09-23 19:02     ` Carlos Rafael Giani
2014-09-23 19:14       ` Richard Cochran
2014-09-23 19:20         ` Carlos Rafael Giani
2014-09-23 19:30           ` Richard Cochran
2014-09-23 19:32             ` Carlos Rafael Giani
2014-09-23 19:52               ` Richard Cochran
2014-09-23 19:56                 ` Carlos Rafael Giani
2014-09-23 19:57                 ` Otavio Salvador
2014-09-23 20:12                   ` Richard Cochran
2014-09-23 20:27                     ` Otavio Salvador
2014-09-23 20:42                       ` Richard Cochran
2014-09-23 20:46                         ` Carlos Rafael Giani
2014-09-24  4:50                           ` Richard Cochran
2014-09-24 16:42                             ` Eric Nelson [this message]
2014-09-24 17:05                               ` Richard Cochran
2014-09-24  8:58                       ` Richard Cochran
2014-09-24 11:21                         ` Otavio Salvador
2014-09-24 12:07                           ` Richard Cochran
2014-09-24 15:28                             ` Daiane Angolini
2014-09-24 15:32                         ` Bin Lin
2014-09-23 19:26       ` Bin Lin
2014-09-23 19:29         ` Carlos Rafael Giani
2014-09-23 19:06     ` Richard Cochran
2014-09-23 19:15       ` Carlos Rafael Giani
2014-09-23 19:23         ` Richard Cochran
2014-09-23 19:29           ` Carlos Rafael Giani
2014-09-23 19:39             ` Richard Cochran
2014-09-23 19:44               ` Bin Lin

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=5422F47D.1070009@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=dv@pseudoterminal.org \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    --cc=richardcochran@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.