From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] BSS footprint of FAT very high - SPL issues
Date: Fri, 11 Feb 2011 11:58:20 +0530 [thread overview]
Message-ID: <4D54D704.3060508@ti.com> (raw)
In-Reply-To: <4D4CF506.5090902@free.fr>
Hello Wolfgang, Albert,
On Saturday 05 February 2011 12:28 PM, Albert ARIBAUD wrote:
> Hi Aneesh,
>
> Le 03/02/2011 11:38, Aneesh V a ?crit :
>
>> On second thoughts I would like to keep the entire bss in SDRAM. With
>> MMC and FAT support, the SPL is already nearing the IRAM budget in
>> OMAP3. It helps to save some space by moving out bss to SDRAM.
>>
>> If needed, I can fix up the start.S by defining something like
>> _end_of_data. But is that really needed. I do not see any SPL that
>> needs relocation and SDRAM bss at the same time.
>
> "Patches Welcome" :) -- with added thanks for patching all start.S /
> u-boot.lds in the ARM arch consistently.
I see __u_boot_cmd_end as the end of the image to be relocated in all
the scripts. Shall I use this label for this purpose. This will work
for now and save me from touching all those linker scripts. However,
there is a small possibility of this leading to the same problem as
with __bss_start in future. I don't think that should be a big concern.
Do you agree?
Best regards,
Aneesh
next prev parent reply other threads:[~2011-02-11 6:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 5:23 [U-Boot] BSS footprint of FAT very high - SPL issues Aneesh V
2011-02-01 6:52 ` Bedia, Vaibhav
2011-02-01 7:58 ` Wolfgang Denk
2011-02-01 8:26 ` Aneesh V
2011-02-01 8:35 ` Bedia, Vaibhav
2011-02-01 10:05 ` Wolfgang Denk
2011-02-01 10:18 ` Bedia, Vaibhav
2011-02-01 10:48 ` Albert ARIBAUD
2011-02-01 12:43 ` Bedia, Vaibhav
2011-02-01 13:27 ` Wolfgang Denk
2011-02-01 10:53 ` Albert ARIBAUD
2011-02-11 21:16 ` Ulf Samuelsson
2011-02-11 22:15 ` Wolfgang Denk
2011-09-13 21:40 ` Ulf Samuelsson
2011-09-28 20:28 ` Wolfgang Denk
2011-02-12 6:13 ` Aneesh V
2011-02-01 7:04 ` Albert ARIBAUD
2011-02-01 7:11 ` Albert ARIBAUD
2011-02-01 8:00 ` Wolfgang Denk
2011-02-01 8:27 ` Aneesh V
2011-02-01 7:55 ` Wolfgang Denk
2011-02-01 8:18 ` Aneesh V
2011-02-01 8:48 ` Bedia, Vaibhav
2011-02-01 10:03 ` Wolfgang Denk
2011-02-02 13:17 ` Aneesh V
2011-02-02 13:37 ` Albert ARIBAUD
2011-02-02 14:01 ` Aneesh V
2011-02-02 15:14 ` Albert ARIBAUD
2011-02-03 10:38 ` Aneesh V
2011-02-05 6:58 ` Albert ARIBAUD
2011-02-11 6:28 ` Aneesh V [this message]
2011-02-11 6:39 ` Albert ARIBAUD
2011-02-11 6:57 ` Aneesh V
2011-02-11 8:15 ` Albert ARIBAUD
2011-02-11 8:27 ` Aneesh V
2011-02-02 21:01 ` Graeme Russ
2011-02-03 7:01 ` Aneesh V
2011-02-03 10:05 ` Graeme Russ
2011-02-03 6:49 ` sughosh ganu
2011-02-03 7:22 ` Aneesh V
2011-02-15 8:44 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D54D704.3060508@ti.com \
--to=aneesh@ti.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox