From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Tue, 1 Dec 2015 15:16:29 +0100 Subject: [U-Boot] [PATCH] arm: mx6: Reduce SPL malloc pool size In-Reply-To: References: <1448052204-4928-1-git-send-email-marex@denx.de> <201512010031.57550.marex@denx.de> Message-ID: <201512011516.29849.marex@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tuesday, December 01, 2015 at 03:13:17 PM, Tim Harvey wrote: > On Mon, Nov 30, 2015 at 3:31 PM, 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. > > Marek, Hi Tim, > I checked and Falcon mode does load images directly into RAM so large > malloc still doesn't make sense and should be reduced. I think 1MB is > a fine value. Thank you! Best regards, Marek Vasut