All of lore.kernel.org
 help / color / mirror / Atom feed
From: twebb <taliaferro62@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] fat32 cluster size check
Date: Thu, 12 Mar 2009 16:11:06 -0400	[thread overview]
Message-ID: <dbdb2ea60903121311w7acb9ab8qfb296f7bc7001bda@mail.gmail.com> (raw)

I see that a fix for cluster size checking for fat32 was commited in
8ce4e5...  "Fix checking fat32 cluster size."  One question I have is
that I implemented the fix but still see occasional problems with
fatls and fatload failing with "Invalid FAT entry".  Is the max value
for the new macro CHECK_CLUST() supposed to be 0x0FFF FFF0 (as it is
now) or should it be 0xFFFF FFF0?

The value I'm seeing for curclust returned from get_fatent() =
0xFFFFFF8 which results in the CHECK_CLUST() failure.  This is
occurring in get_vfatname().

I'm seeing the problem on a 4Gbyte SDcard with a 32+Mbyte FAT32
partition.  Any ideas?

Two follow-on questions (that may be way off base):

Do FATBUFBLOCKS need to be increased beyond 6 to support FAT32?
Does u-boot FAT32 support require filenames to be in 8.3 form only, or
are longer filenames supported?

Thanks.

                 reply	other threads:[~2009-03-12 20:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=dbdb2ea60903121311w7acb9ab8qfb296f7bc7001bda@mail.gmail.com \
    --to=taliaferro62@gmail.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.