From mboxrd@z Thu Jan  1 00:00:00 1970
From: michael <trimarchi@gandalf.sssup.it>
Date: Tue, 01 Apr 2008 13:44:50 +0200
Subject: [U-Boot-Users] [PATCH] get_vfatname
In-Reply-To: <20080328235143.76136248BF@gemini.denx.de>
References: <20080328235143.76136248BF@gemini.denx.de>
Message-ID: <47F22032.6040409@gandalf.sssup.it>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Wolfgang Denk wrote:
> 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
>
>   
I can give you an image that you can write on ide disk or on a Compact 
Flash.
Is ok?

Michael