From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Babic Date: Tue, 1 Dec 2015 15:18:00 +0100 Subject: [U-Boot] [PATCH] arm: mx6: Reduce SPL malloc pool size In-Reply-To: <201512010031.57550.marex@denx.de> References: <1448052204-4928-1-git-send-email-marex@denx.de> <201511251432.25058.marex@denx.de> <201512010031.57550.marex@denx.de> Message-ID: <565DAC18.1040808@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 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 =====================================================================