From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot spl with fat32 on arm
Date: Wed, 29 Jan 2014 16:57:49 -0500 [thread overview]
Message-ID: <20140129215749.GT3277@bill-the-cat> (raw)
In-Reply-To: <52E7BD5B.8020702@monstr.eu>
On Tue, Jan 28, 2014 at 03:23:23PM +0100, Michal Simek wrote:
> Hi guys,
>
> I do play a little bit with u-boot spl and I am curious
> about fat32 implementation. There is MAX_CLUSTSIZE which is 65k
> and there are 3 buffers in fat.c code
> do_fat_read_at_block
> get_contents_vfatname_block
> get_dentfromdir_block
>
> All these 3 are placed to bss section.
> I have just 192k of memory for SPL that's why I tried 2 things
> 1. Place these 3 fat arrays to different memory which is working fine
> 2. Decrease MAX_CLUSTSIZE to any low value (I do use 8k).
>
> Unfortunately if I decrease MAX_CLUSTSIZE and add them to bss section
> SPL doesn't work. If I add them to a different section in front of
> or behind bss everything is just fine.
>
> That's why I have a question where can be the problem in this behaviour
> that keeping 8k MAX_CLUSTSIZE in bss section doesn't work
> and keeping 8k MAX_CLUSTSIZE out of bss section works.
>
> bss relocation is not done in SPL.
To be clear, are you saying you cannot do this in your case? We support
CONFIG_SPL_BSS_START_ADDR / CONFIG_SPL_BSS_MAX_SIZE which is how on TI
platforms for example we put BSS into DDR, as we've configured that
before needing BSS.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140129/171c59a6/attachment.pgp>
next prev parent reply other threads:[~2014-01-29 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 14:23 [U-Boot] u-boot spl with fat32 on arm Michal Simek
2014-01-29 21:57 ` Tom Rini [this message]
2014-01-30 7:35 ` Michal Simek
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=20140129215749.GT3277@bill-the-cat \
--to=trini@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