From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] BSS footprint of FAT very high - SPL issues
Date: Fri, 11 Feb 2011 22:16:44 +0100 [thread overview]
Message-ID: <4D55A73C.6090404@atmel.com> (raw)
In-Reply-To: <4D47C3C0.7060806@ti.com>
2011-02-01 09:26, Aneesh V skrev:
> Hi Vaibhav,
>
> On Tuesday 01 February 2011 12:22 PM, Bedia, Vaibhav wrote:
>> Hi Aneesh,
>>
>> On Tuesday, February 01, 2011 10:54 AM, Aneesh V wrote:
>>> Dear Wolfgang,
>>>
>>> I had been working on creating an MMC SPL for OMAP4. OMAP boards
>>> typically support booting from the FAT partition of a removable
>>> SD/MMC card. So, we need to have FAT support in the SPL. But I am
>>> having some difficulties in adding FAT support to SPL.
>>>
>>> BSS footprint of fat.c is very high. It has three buffers each of
>>> size 64KB. To workaround this problem I have done something like
>>> below(The way x-loader works around this problem today).
>>> CONFIG_SYS_SPL_FAT_BUFFER_BASE is in SDRAM.Is this ok?
>>>
>> [...]
>>
>> I guess you will hit a similar issue with the networking related code is used (I am not sure if SPL uses it). That also requires a decent size of bss.
> Luckily we don't need networking related code in SPL.
>
> I would prefer to have rest of the BSS in internal RAM itself.
>
> best regards,
> Aneesh
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
The way this problem is fixed on the AT91 is to run at91bootstrap first.
This program will initialize the SDRAM and copy u-boot to SDRAM.
at91bootstrap fits into 4 kB of code, and a small amount of RAM,
so it will run on real small CPUs.
You could try to do the same, instead of spending a lot of time,
trying to optimize.
--
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2011-02-11 21:16 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 [this message]
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
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=4D55A73C.6090404@atmel.com \
--to=ulf.samuelsson@atmel.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