From: Nick Garnett <nickg@ecoscentric.com>
To: "Scott Bailie" <bailie@ll.mit.edu>
Cc: <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] fat filename length
Date: Thu, 20 Apr 2006 09:31:00 -0000 [thread overview]
Message-ID: <m3r73s61ax.fsf@xl5.calivar.com> (raw)
In-Reply-To: <200604192224.k3JMOKIj005435@ll.mit.edu>
"Scott Bailie" <bailie@ll.mit.edu> writes:
> I've noticed that only 8.3 filenames under FAT. I poked around in
> fatfs_supp.c where it looks like this limitation is hard coded. Has anyone
> made the necessary changes to support long filenames? Is there any plan to
> do so?
Long file names require quite a lot of changes to the filesystem. We
(eCosCentric) have added LFN support to our version of the FATFS. This
is currently available through our eCosPro product.
There are also patent issues with Microsoft, which means that many
commercial users are reluctant to use LFN at present.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2006-04-20 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 22:24 Scott Bailie
2006-04-20 1:24 ` [ECOS] Re: Intel LXT971 yh
2006-04-20 2:10 ` Gary Thomas
2006-04-20 4:03 ` yh
2006-04-20 13:21 ` [ECOS] 回复： " hui liu
2006-04-20 9:31 ` Nick Garnett [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=m3r73s61ax.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=bailie@ll.mit.edu \
--cc=ecos-discuss@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).