From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 12 Apr 2013 08:37:12 -0400 Subject: [U-Boot] [PATCH v3 0/4] Homogeneize semantics of CONFIG_SPL_MAX_SIZE In-Reply-To: <1365767743-23585-1-git-send-email-albert.u.boot@aribaud.net> References: <1365549295-9388-1-git-send-email-albert.u.boot@aribaud.net> <1365767743-23585-1-git-send-email-albert.u.boot@aribaud.net> Message-ID: <20130412123712.GM9914@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, Apr 12, 2013 at 01:55:39PM +0200, Albert ARIBAUD wrote: > CONFIG_SPL_MAX_SIZE and CONFIG_SPL_BSS_MAX_SIZE did not have constant > semantics across all of U-boot. This patch series aims at fixing this by > splitting the maximum size into separate image (code + data + rodata + > linker list) size on the one hand, and BSS size on the other hand. > > Changes in v3: > - introduced CONFIG_SPL_MAX_FOOTPRINT > - fixed typo in BSS size test > > Changes in v2: > - brought back total size to 12K > - fixed commit summary typoes > - fixed spacing in commit summary > - removed mmutable in SPL linker file > > Albert ARIBAUD (4): > cam_enc_4xx: fix CONFIG_SPL_MAX_SIZE semantics > da850evm, da850_am18xxevm: fix CONFIG_SPL_MAX_SIZE semantics > smdk5250, snow: fix CONFIG_SPL_MAX_SIZE semantics > ARM: fix CONFIG_SPL_MAX_SIZE semantics The problem is that cam_enc_4xx, da850* and quite likely smdk5250 all want the new CONFIG_SPL_MAX_FOOTPRINT and not an arbitrary split between BSS and everything else. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: