All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] FAT errors
Date: Fri, 6 Sep 2019 00:22:02 +0200	[thread overview]
Message-ID: <fc1c6c5d-9593-f7ee-2131-f023e99174f3@gmx.de> (raw)
In-Reply-To: <23aa7eec-9772-d689-4799-d264d63dcb2f@wwwdotorg.org>

On 9/5/19 5:23 PM, Stephen Warren wrote:
> On 9/5/19 6:22 AM, Heinrich Schuchardt wrote:
>> On 9/5/19 2:06 PM, Tom Rini wrote:
>>> On Thu, Sep 05, 2019 at 08:43:43AM +0200, Heinrich Schuchardt wrote:
>>>> Currently we do no have a maintainer for the FAT file system. Takahiro
>>>> has done a great job fixing some of the most prominent deficiencies.
>>>> But
>>>> still the driver is not in good shape:
>>>>
>>>> I once again ran upon errors in FAT when executing the UEFI SCT.
>>>>
>>>> Here is some of the output of
>>>> dosfsck -w -r -l -a -v -t
>>>> The full output has hundreds of errors recorded.
>>>>
>>>> Orphaned long file name part "Sct.log"
>>>>    Auto-deleting.
>>>> Orphaned long file name part "Sct.log"
>>>>    Auto-deleting.
>>>> /Log/RuntimeServicesTest/VariableServicesTest0/QueryVariableInfo_Conf_0_0_61758774-91A3-47DD-BDBD-B81094A5F62D.log
>>>>
>>>>    Duplicate directory entry.
>>>>    First    Size 4712 bytes, date 01:00:00 Dec 31 1979
>>>>    Second   Size 5086 bytes, date 01:00:00 Dec 31 1979
>>>>    Auto-renaming second.
>>>>    Renamed to FSCK0000.008
>>>>
>>>> BareBox is using a (somewhat outdated) copy of this library with a
>>>> little bit of wrapper code:
>>>>
>>>> FatFs - Generic FAT Filesystem Module
>>>> http://elm-chan.org/fsw/ff/00index_e.html
>>>> http://elm-chan.org/fsw/ff/arc/ff13c.zip
>>>>
>>>> The same library is also used for Arduinos:
>>>> https://github.com/stm32duino/FatFs
>>>>
>>>> Shouldn't we try just the same?
>>>
>>> I think that or similar has been suggested before.  Are you volunteering
>>> to maintain the wrapper and keep it in-sync?  Thanks!
>>>
>>
>> Here is the reference
>>
>> Stephen Warren
>> [PATCH 0/9] Replace the FAT filesystem code
>> https://lists.denx.de/pipermail/u-boot/2015-August/222545.html
>
> IIRC, we abandoned that effort since ff turned out to be very slow. I'm
> not sure whether adding a disk caching library underneath it would have
> helped or not. Probably you can find those discussions from the mailing
> list post above?
>
> Another FAT implementation that might be worth looking at is from FreeRTOS:
>
> https://freertos.org/FreeRTOS-Plus/FreeRTOS_Plus_FAT/index.html
>
> FreeRTOS itself recently got bought by Amazon and switched to an MIT
> license. I assume the same is true of their FAT code. So, should be OK
> to integrate.
>

Thanks for the link. The MIT license has been applied to Free RTOS plus
FAT. It seems to much more code than what ElmChan wrote. So we will have
to look check the increase of U-Boot.

Best regards

Heinrich

      reply	other threads:[~2019-09-05 22:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05  6:43 [U-Boot] [RFC] FAT errors Heinrich Schuchardt
2019-09-05  8:37 ` AKASHI Takahiro
2019-09-07 23:49   ` Heinrich Schuchardt
2019-09-10  0:53     ` AKASHI Takahiro
2019-09-10  7:20       ` Heinrich Schuchardt
2019-09-05 12:06 ` Tom Rini
2019-09-05 12:22   ` Heinrich Schuchardt
2019-09-05 15:23     ` Stephen Warren
2019-09-05 22:22       ` Heinrich Schuchardt [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=fc1c6c5d-9593-f7ee-2131-f023e99174f3@gmx.de \
    --to=xypron.glpk@gmx.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 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.