FAT for NAND Flash --> Use of OOB

Charles Manning manningc2 at actrix.gen.nz
Sun May 19 19:58:27 EDT 2002

On Sat, 18 May 2002 17:16, Yong-iL Joh wrote:
> Studying MTD <studying_mtd at yahoo.com> writes:
> > If i want to use FAT with NAND then i have to use :-
> >
> > A. FAT: filesystem driver
> > B. Translation: Translation layer
> > C. MTD: Memory Technology Devices driver
> > D. NAND: generic NAND driver
> > E. Hardware specific driver
> >
> > So i have to add only Translation layer, rest layers
> > will remain same.
> >
> > Am i right ? If not, please correct me.
> >
> > How can i write traslation layer , any reference.
> IMHO, you're right.
> we have implemented this way for SMC(SmartMedia Card). :)
> but, we can't use current MTD's nand.c because of different usage of OOB.
> we called SMCTL as "B. Translation".

Can you be more specific about the issue here? I'm interested as there might 
be some synergy.

I have a different file system (not JFFSx) that uses nand.c, but  the 
interface provided by nand.c is not optimal.

What I did is write some wrapper functions to map from the way I like to see 
NAND ( probably a bit more like SMFS) and the functions provided by nand.c

In the short term, writing your own wrappers is the way to go since it 
buffers your code from the mtd nand interface.
In the longer term, the mtd nand interface might expose more functions to to 
more SM friendly.

-- Charles

More information about the linux-mtd mailing list