From: Rutger Hofman <rutger@cs.vu.nl>
To: Himanshu Patel <himanshup@aftek.com>
Cc: "'eCos Discuss'" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] FAT32 over NAND
Date: Tue, 20 Jan 2009 15:40:00 -0000 [thread overview]
Message-ID: <4975F117.1040709@cs.vu.nl> (raw)
In-Reply-To: <000901c97b11$b124cfd0$136e6f70$@com>
Himanshu Patel wrote:
> Okay...Thanks...
>
> YAFFS2 is not a possible option...As device should also be able to access on
> Windows PC using mass storage interface...
Is this a NAND memory smart-card (MMC, SD, USB flash drive or whatever)?
These usually come with an FTL on-board, which offers a file system like
FAT32. You need no Flash code for that.
Is this a raw flash? So, how is it going to be accessed from Windows if
the file system is completely in software?
> Can we use NFTL (NAND flash translation layer) support provided by Linux?
I am no Linux expert, but my feeling is that NFTL is very old, and that
flash handling is done through UBI/UBIFS. The UBIFS link in my message
below seems rather informative.
Rutger
> Regards,
>
> Himanshu Patel
>
> -----Original Message-----
> From: Rutger Hofman [mailto:rutger@cs.vu.nl]
> Sent: Tuesday, January 20, 2009 8:15 PM
> To: Himanshu Patel; 'eCos Discuss'
> Subject: Re: [ECOS] FAT32 over NAND
>
> Andrew Lunn wrote:
>> On Tue, Jan 20, 2009 at 07:38:02PM +0530, Himanshu Patel wrote:
>>> Hi,
>>>
>>> We want to have FAT32 file system over NAND flash. Is it possible? What
>>> approach should we take for developing the same?
>> If you look back in the archive, last year there was some work to get
>> YAFFS on NAND working. I would suggest trying to build on the NAND
>> infrastructure that provided.
>
> I implemented basic NAND flash functionality and a wrapper layer for
> YAFFS2, a file system designed specifically for NAND flash. For an alpha
> release (and maybe later on, beta release) of my code, see:
> http://www.cs.vu.nl/~rutger/software/ecos/nand-flash/
>
> If you want FAT32, you will have to create (port from elsewhere?) a FTL
> (Flash Translation Layer) that implements lots of stuff to make FAT32
> behave in a NAND-compatible way. For a discussion of this in the context
> of UBIFS (the latest-greatest Linux NAND flash file system), see:
>
> http://www.linux-mtd.infradead.org/doc/ubifs.html#L_raw_vs_ftl
>
> An FTL should minimally provide:
> - wear levelling
> - garbage collection for released blocks
> - bad block management
> - write caching because programming has to be consecutive and in at most
> a few operations.
>
> YAFFS2 implements all this already. Is using YAFFS2 an option, maybe?
>
> Rutger Hofman
> VU Amsterdam
>
>
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-01-20 15:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 14:50 [ECOS] Size of eCos Himanshu Patel
2009-01-20 14:08 ` [ECOS] FAT32 over NAND Himanshu Patel
2009-01-20 14:31 ` Andrew Lunn
2009-01-20 14:40 ` Himanshu Patel
2009-01-20 14:42 ` Rutger Hofman
2009-01-20 15:11 ` Himanshu Patel
2009-01-20 15:15 ` Andrew Lunn
2009-01-20 15:17 ` Himanshu Patel
2009-01-20 18:42 ` Jonathan Larmour
2009-01-20 19:09 ` Paul D. DeRocco
2009-01-21 2:18 ` Jonathan Larmour
2009-01-21 4:26 ` Paul D. DeRocco
2009-01-20 15:14 ` Himanshu Patel
2009-01-20 15:40 ` Rutger Hofman [this message]
2009-01-20 16:30 ` Chris Zimman
2009-01-21 13:59 ` Rutger Hofman
2009-01-21 14:08 ` Himanshu Patel
2009-01-21 20:18 ` Rutger Hofman
2009-01-21 20:54 ` Paul D. DeRocco
2009-01-21 14:12 ` Himanshu Patel
2009-01-21 16:12 ` Chris Zimman
2009-01-21 14:14 ` Himanshu Patel
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=4975F117.1040709@cs.vu.nl \
--to=rutger@cs.vu.nl \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=himanshup@aftek.com \
/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).