All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: mx6: Reduce SPL malloc pool size
Date: Tue, 1 Dec 2015 15:18:00 +0100	[thread overview]
Message-ID: <565DAC18.1040808@denx.de> (raw)
In-Reply-To: <201512010031.57550.marex@denx.de>

Hi Marek,

On 01/12/2015 00:31, Marek Vasut wrote:

>>
>> Perhaps the use case for a >1MB malloc area is falcon mode. While a
>> 1MB area certainly works for loading and bootstrapping to u-boot.img I
>> have used anywhere from 1MB to 8MB images for falcon mode.
> 
> Does the falcon mode load the image into malloc'd area or directly into
> RAM location ? If it's the former, then yeah, large malloc pool makes
> sense and MALLOC_CLEAR_ON_INIT makes sense as well I guess.

No, it copies directly into the RAM.  Large malloc area are not needed
for Falcon Mode, and I have not idea who needs a large area. More as
instantiating SPI or I2C is generally not needed.

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

      parent reply	other threads:[~2015-12-01 14:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 20:43 [U-Boot] [PATCH] arm: mx6: Reduce SPL malloc pool size Marek Vasut
2015-11-20 21:24 ` Stefano Babic
2015-11-20 21:40 ` Tim Harvey
2015-11-25 10:40   ` Przemyslaw Marczak
2015-11-25 10:56     ` Marek Vasut
2015-11-25 12:00       ` Przemyslaw Marczak
2015-11-25 12:16         ` Marek Vasut
2015-11-25 13:15           ` Przemyslaw Marczak
2015-11-25 13:32             ` Marek Vasut
2015-11-30 18:56               ` Tim Harvey
2015-11-30 23:31                 ` Marek Vasut
2015-12-01 14:13                   ` Tim Harvey
2015-12-01 14:16                     ` Marek Vasut
2015-12-01 14:18                   ` Stefano Babic [this message]

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=565DAC18.1040808@denx.de \
    --to=sbabic@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.