All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] BSS footprint of FAT very high - SPL issues
Date: Tue, 01 Feb 2011 13:48:17 +0530	[thread overview]
Message-ID: <4D47C1C9.1020002@ti.com> (raw)
In-Reply-To: <20110201075521.60484B187@gemini.denx.de>

Dear Wolfgang,

On Tuesday 01 February 2011 01:25 PM, Wolfgang Denk wrote:
> Dear Aneesh V,
>
> In message<4D4798E2.3050500@ti.com>  you wrote:
>>
>> 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?
>
> Why would that be necessary?  Just put the BSS segment in SDRAM, and
> everything is fine, isn't it?

SDRAM is initialized by the SPL. So, bss can not be initialized and
used until SDRAM initialization is complete. I would prefer to have
rest of the bss in internal RAM so that it's available as soon as we
enter C code.

>
>> Also, I was wondering why we need 3 such scratch buffers in this
>> implementation. I do not understand this code. But I was wondering if we
>> could work with just one 64K buffer?
>
> I have no idea.   I am not familiar with that code either.

Probably I will give it a try once I solve some other issues I am
facing in getting FAT to work.

Best regards,
Aneesh

  reply	other threads:[~2011-02-01  8:18 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 [this message]
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=4D47C1C9.1020002@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.