From: "luoxiao" <luoxiao@roxus.net>
To: linux-mtd@lists.infradead.org
Subject: best nand flash fs for 2.0.38 kernel?
Date: Fri, 9 Jan 2004 15:07:23 +0800 [thread overview]
Message-ID: <20040109150723.M52805@roxus.net> (raw)
Hi, all
I'm currently trying to add nand flash file system support for the linux
2.0.38 porting on my company's product. I choosed the JFFS but the JFFS2
because it fits the old 2.0.x kernel. In the processing of porting I met a
lot of troubles and I thought some of them are caused by bugs of JFFS code
rather by my porting. So a question is: is the JFFS stable enough for product
usage? I saw it is still in the fs/ directory of the brand-new 2.6.0 kernel.
Does this fact mean that the version of JFFS in the 2.6.0 kernel is stable
enough to use? I've searched the docs and mail archive but it seems that no
one is using JFFS now. So the question is: what is the best nand flash file
system for the 2.0.x kernel?
Any hints are appreciated, thanks!
Xiao Luo
Operating System Dept.
Roxus Tech.
next reply other threads:[~2004-01-09 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 7:07 luoxiao [this message]
2004-01-12 18:17 ` best nand flash fs for 2.0.38 kernel? 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=20040109150723.M52805@roxus.net \
--to=luoxiao@roxus.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox