All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yong-iL Joh <tolkien@mizi.com>
To: Studying MTD <studying_mtd@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: FAT for NAND Flash
Date: 20 May 2002 12:39:48 +0900	[thread overview]
Message-ID: <hblmafa3nf.fsf@tolkien.mizi.com> (raw)
In-Reply-To: <20020518153031.25391.qmail@web21508.mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

Studying MTD <studying_mtd@yahoo.com> writes:

> --- Yong-iL Joh <tolkien@mizi.com> wrote:
> > 1. FAT (of Linux)
> > 2. SCMTL (similar to FTL, NFTL,...)
> 
> what is SCMTL ? 
> from where i can get specs of SCMTL.

Oh, mistype! SMCTL.
just name it for convenience.
Smart Media Card Translation Layer. :-)

> is it also having patent ?

I don't know, see SSFDC forum about that.

> > 3. NAND_smc (it's almost same NAND in MTD except
> > handling ECC)
> 
> then how you handle ECC ?

ECC algorithm is same. but different mapping of data in OOB

In SMFS by SSFDC, for the 512+16 bytes/pages models
usage of OOB is following

512 ~ 515       reserved
516             Data Status Byte
517             Block Status Byte
518,519         Block Address Field-1
520~522         ECC Field-2
523,524         Block Address Field-2
525~527         ECC Field-1

> from where i can get your source code.
> Is it working properly .

attatched source of driver is working properly based in 2.4.16-rmk2.
so mtd layer is a bit older.
(if this distribution is illegal, please do not use for commercial.
 I'm not lawyer. :p )

[-- Attachment #2: SMC by mizi --]
[-- Type: application/octet-stream, Size: 25325 bytes --]

[-- Attachment #3: Type: text/plain, Size: 63 bytes --]


-- 
Joh, Yong-iL
E-mail: tolkien@nownuri.net tolkien@mizi.com

  reply	other threads:[~2002-05-20  3:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-16 14:14 FAT for NAND Flash Studying MTD
2002-05-16 14:24 ` David Woodhouse
2002-05-16 14:46   ` Studying MTD
2002-05-16 15:08     ` David Woodhouse
2002-05-16 16:31       ` Paul
2002-05-16 17:35         ` David Woodhouse
2002-05-16 20:34           ` Paul
2002-05-17  6:03             ` David Woodhouse
2002-05-17  6:40               ` Paul
2002-05-18  5:16     ` Yong-iL Joh
2000-01-12 11:37       ` Thomas Gleixner
2002-05-18  7:19       ` David Woodhouse
2002-05-19 23:58       ` FAT for NAND Flash --> Use of OOB Charles Manning
2002-05-17 13:44   ` FAT for NAND Flash Studying MTD
2002-05-17 13:50     ` David Woodhouse
2002-05-17 14:00       ` Studying MTD
2002-05-17 14:39         ` David Woodhouse
2002-05-17 16:19           ` Studying MTD
2002-05-18 16:00             ` David Woodhouse
2002-05-18 17:53               ` Studying MTD
2002-05-18 18:20               ` Studying MTD
2002-05-19  9:34                 ` David Woodhouse
2002-05-19 23:26                   ` Newby question Charles Manning
2002-05-20  6:49                     ` David Woodhouse
2002-05-20  7:48                       ` Newby question --> source tree management Charles Manning
2002-05-18  5:13 ` FAT for NAND Flash Yong-iL Joh
2002-05-18 15:30   ` Studying MTD
2002-05-20  3:39     ` Yong-iL Joh [this message]
2002-05-20 11:36       ` Studying MTD
2002-05-21 10:52         ` Yong-iL Joh
2002-05-21 22:36           ` Charles Manning

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=hblmafa3nf.fsf@tolkien.mizi.com \
    --to=tolkien@mizi.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=studying_mtd@yahoo.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 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.