From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fat: Define MAX_CLUSTSIZE only if not defined in config
Date: Mon, 12 May 2014 14:58:48 -0400 [thread overview]
Message-ID: <20140512185848.GF22182@bill-the-cat> (raw)
In-Reply-To: <5ea5a3ef17e45dadd3e5a39870436b7a56785c27.1398433682.git.michal.simek@xilinx.com>
On Fri, Apr 25, 2014 at 03:48:04PM +0200, Michal Simek wrote:
> From: Siva Durga Prasad Paladugu <siva.durga.paladugu@xilinx.com>
>
> Define MAX_CLUSTSIZE only if not defined in board specific
> config file as this size can be decreased to save memory
> in some memory constrained cases.
>
> Signed-off-by: Siva Durga Prasad Paladugu <sivadur@xilinx.com>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
>
> include/fat.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/fat.h b/include/fat.h
> index c8eb7cc..1213060 100644
> --- a/include/fat.h
> +++ b/include/fat.h
> @@ -18,7 +18,9 @@
> #define VFAT_MAXSEQ 9 /* Up to 9 of 13 2-byte UTF-16 entries */
> #define PREFETCH_BLOCKS 2
>
> +#ifndef MAX_CLUSTSIZE
> #define MAX_CLUSTSIZE 65536
> +#endif
> #define DIRENTSPERBLOCK (mydata->sect_size / sizeof(dir_entry))
> #define DIRENTSPERCLUST ((mydata->clust_size * mydata->sect_size) / \
> sizeof(dir_entry))
Sorry for the delay. This should be CONFIG_FS_FAT_MAX_CLUSTSIZE and
documented in the README.
--
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/20140512/aa3e467d/attachment.pgp>
prev parent reply other threads:[~2014-05-12 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 13:48 [U-Boot] [PATCH] fat: Define MAX_CLUSTSIZE only if not defined in config Michal Simek
2014-05-06 12:21 ` Michal Simek
2014-05-12 18:58 ` Tom Rini [this message]
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=20140512185848.GF22182@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