From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Thu, 11 Apr 2013 10:14:10 -0600 Subject: [U-Boot] [PATCH v2 4/4] ARM: fix CONFIG_SPL_MAX_SIZE semantics In-Reply-To: <20130411160820.GH9914@bill-the-cat> References: <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> <5165E602.5040700@wwwdotorg.org> <20130411005001.56efc6a3@lilith> <20130411010954.2fc374de@lilith> <5165F2E1.2010404@wwwdotorg.org> <20130411163253.35b11644@lilith> <20130411160820.GH9914@bill-the-cat> Message-ID: <5166E152.40005@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 04/11/2013 10:08 AM, Tom Rini wrote: ... > To be clear, I think the fake partitioning scheme we use when the > case is "we care about text/data/rodata/bss fitting in $X" is not > optimal, but it covers all of the cases without adding more > complexity / another way to achieve the same ends. But it does add more complexity; somebody has to pick, and potentially keep adjusting, the split between text/rodata/data and bss, even though they don't care about that split, but it's an implementation wart. It's also trivial to fix it properly as I described. But, if it absolutely has to be that way, then OK. However, I would ask that at least the Tegra board configuration files be set up so that the previous overall restriction (bss doesn't overlap the main U-Boot) be left in tact, so we don't have to debug that problem again.