From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Wed, 10 Apr 2013 16:21:54 -0600
Subject: [U-Boot] [PATCH v2 4/4] ARM: fix CONFIG_SPL_MAX_SIZE semantics
In-Reply-To: <1365549295-9388-5-git-send-email-albert.u.boot@aribaud.net>
References: <1365451109-22030-1-git-send-email-albert.u.boot@aribaud.net>
	<1365549295-9388-1-git-send-email-albert.u.boot@aribaud.net>
	<1365549295-9388-2-git-send-email-albert.u.boot@aribaud.net>
	<1365549295-9388-3-git-send-email-albert.u.boot@aribaud.net>
	<1365549295-9388-4-git-send-email-albert.u.boot@aribaud.net>
	<1365549295-9388-5-git-send-email-albert.u.boot@aribaud.net>
Message-ID: <5165E602.5040700@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 04/09/2013 05:14 PM, Albert ARIBAUD wrote:
> Remove SPL-related ASSERT() in arch/arm/cpu/u-boot.lds
> as this file is never used for SPL builds.
> 
> Rewrite the ASSERT() in arch/arm/cpu/u-boot-spl.lds
> to separately test image (text,data,rodata...) size
> and BSS size each against its own max.
> 
> Also, output section mmutable is not used in SPL builds.
> Remove it.
> 
> Finally, update README regarding the (now homogeneous)
> semantics of the CONFIG_SPL_MAX_SIZE and
> CONFIG_SPL_BSS_MAX_SIZE macros.

This still seems to have separate defines for SPL text/data/rodata size
and BSS size. If I want instead to limit the total text/data/rodata/bss
size, but place no specific limit on the bss size individually, can I
not do that?