From: michael <trimarchi@gandalf.sssup.it>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] get_vfatname
Date: Fri, 28 Mar 2008 11:06:03 +0100 [thread overview]
Message-ID: <47ECC30B.9030002@gandalf.sssup.it> (raw)
In-Reply-To: <20080327145257.29C6F248BE@gemini.denx.de>
Hi,
Wolfgang Denk wrote:
> In message <47EB9C97.8030000@gandalf.sssup.it> you wrote:
>
>> I find a problem related to the get_vfatname function. This is my
>> proposal patch.
>>
>
> What exactly is the preoblem? Is there a test case that can reproduce
> the problem?
>
My test case is a 64Mb CF. Maybe I give you a link :) as soon as possible.
The problem is that the code doesn't look if the dir_slot contain a long
name.
If doesn't contain a long name is a dir_entry and the name can be get by the
get_name function. I'm not an expert of vfat filesystem, I take a look
to the
linux code and to experimental result. The block that is read by the
gc_getcluster function is not a dir_slot but a dir_entry.
Regards Michael
next prev parent reply other threads:[~2008-03-28 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 13:09 [U-Boot-Users] [PATCH] get_vfatname michael
2008-03-27 14:52 ` Wolfgang Denk
2008-03-28 10:06 ` michael [this message]
2008-03-28 11:37 ` michael
2008-03-28 23:51 ` Wolfgang Denk
2008-04-01 11:44 ` michael
2008-04-01 12:45 ` Wolfgang Denk
2008-04-04 10:30 ` michael
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=47ECC30B.9030002@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--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