All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jim Zeus <jimzeus@vip.sina.com>
Cc: MTD mail list <linux-mtd@lists.infradead.org>
Subject: Re: [SPAM] FAT on NAND
Date: Mon, 07 Apr 2003 10:01:03 +0200	[thread overview]
Message-ID: <200304071001.03442.tglx@linutronix.de> (raw)
In-Reply-To: <005001c2fcb6$553cf1a0$2a00a8c0@zhengjun>

On Monday 07 April 2003 05:32, Jim Zeus wrote:
> > For what ? Why don't you use JFFS2 or YAFFS, which handle NAND out of the
> > box ?
> Because I've got to build a FS which can be accessed by Windows and Linux
> at the same time.I think JFFS2/YAFFS can't be recognized by Windows
> nowadays. And , it seems like I have to support some device layer between
> the FS and Flash so the Linux can access it, isn't it?
> Is there anyway else I can choose?
No, but AFAIK is there a Windows driver for YAFFS. 
 
> Are all the functions supported by JFFS2/YAFFS? Somebody told me the wear
> levelling is supported by MTD
Crap, MTD just provides the low level interface. Bad block management, wear 
levelling and journalling must be done in the fs driver.

> Does the SMART-Media-FAT build directly on a _bare_ NAND Flash ? 
> If it is, That's nothing useful to me 'cause Linux cant access it.
You can build it on bare FLASH: But that's not the correct way for LINUX. Your 
have to build a filesystem driver, which acts on top of MTD.

1. fs-driver 
2. MTD-block-device-driver
3. MTD-partition-driver
4. Generic NAND-driver
5. yourHardwareInterface-driver

2, 3 and 4 exist.
5 is easy to build (copy an existing one and modify it to fit your hardware)

1 has to be written from scratch. 
The specifications of SmartMedia-FAT are available from
http://www.ssfdc.or.jp/english/index.htm


-- 
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  reply	other threads:[~2003-04-07  7:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04  6:21 [SPAM] FAT on NAND jimzeus
2003-04-04  9:40 ` David Woodhouse
2003-04-07  3:19   ` Jim Zeus
2003-04-07 14:32     ` Jörn Engel
2003-04-07 22:49     ` Charles Manning
2003-04-04 10:48 ` Thomas Gleixner
2003-04-07  3:32   ` Jim Zeus
2003-04-07  8:01     ` Thomas Gleixner [this message]
2003-04-04 20:08 ` 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=200304071001.03442.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=jimzeus@vip.sina.com \
    --cc=linux-mtd@lists.infradead.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 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.