From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] get_vfatname
Date: Sat, 29 Mar 2008 00:51:43 +0100 [thread overview]
Message-ID: <20080328235143.76136248BF@gemini.denx.de> (raw)
In-Reply-To: Your message of "Fri, 28 Mar 2008 12:37:12 +0100." <47ECD868.3040600@gandalf.sssup.it>
In message <47ECD868.3040600@gandalf.sssup.it> you wrote:
>
> > 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.
Well, maybe you can give me a test case?
Like some script to create the needed directories / files in a VFAT
file system which provokes the error?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A direct quote from the Boss: "We passed over a lot of good people to
get the ones we hired."
next prev parent reply other threads:[~2008-03-28 23:51 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
2008-03-28 11:37 ` michael
2008-03-28 23:51 ` Wolfgang Denk [this message]
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=20080328235143.76136248BF@gemini.denx.de \
--to=wd@denx.de \
--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