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 10:53:46 +0530 [thread overview]
Message-ID: <4D4798E2.3050500@ti.com> (raw)
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?
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?
---
+#ifdef CONFIG_PRELOADER
+__u8 *get_vfatname_block = (__u8 *)CONFIG_SYS_SPL_FAT_BUFFER_BASE;
+#else
__attribute__ ((__aligned__ (__alignof__ (dir_entry))))
__u8 get_vfatname_block[MAX_CLUSTSIZE];
+#endif
.
.
.
+#ifdef CONFIG_PRELOADER
+__u8 *get_dentfromdir_block = (__u8 *)CONFIG_SYS_SPL_FAT_BUFFER_BASE +
+ MAX_CLUSTSIZE;
+#else
__attribute__ ((__aligned__ (__alignof__ (dir_entry))))
__u8 get_dentfromdir_block[MAX_CLUSTSIZE];
+#endif
+
Best regards,
Aneesh
next reply other threads:[~2011-02-01 5:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 5:23 Aneesh V [this message]
2011-02-01 6:52 ` [U-Boot] BSS footprint of FAT very high - SPL issues 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
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=4D4798E2.3050500@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.