From: "carl liao" <carlliao@21cn.com>
To: "dedekind@infradead.org" <dedekind@infradead.org>
Cc: linux mtd <linux-mtd@lists.infradead.org>
Subject: NAND Flash Device and JFFS2 support
Date: Thu, 21 Apr 2005 17:28:41 +0800 [thread overview]
Message-ID: <Pt949578826864.08914@send1.inner-21cn.com> (raw)
HI Artem,
On 2005-04-20 23:15:01, Artem B. Bityuckiy at dedekind@infradead.org wrote:
>On Wed, 2005-04-20 at 22:47 +0800, carl liao wrote:
>>I back ported mtd snapshot 20050416 codes to 2.4.26 for AMD Au1200.
>>The NAND device could be identified and accessed via /dev/mtd/0.
>>I even could mount /dev/mtdblock/0, copy file to it and umount it.
>>But there is so many warnings or ecc error messages!
>
>This is not normal that you see "so many warnings or ecc error
>messages". Presumably you have problems with your driver.
>
So I will double check my NAND chip driver first of all.
>>So in order to properly use NAND Flash, how could I format and
>>read/write data to it?
>
>flash_eraseall -j to format.
>
>Please, investigate carefully web site at
>http://www.linux-mtd.infradead.org/index.html
>
Thanks all! I found a good post "Can you really write a jffs2 image with
nandwrite?"
at http://lists.infradead.org/pipermail/linux-mtd/2005-March/012045.html
>>I want to put Linux root file system on the NAND. Is it a right choice?
>
>Depends on your requirements.
>
>JFFS2 is a generally good choice if:
> * you need on-flight compression
> * you need unclean-reboot tolerance
> * your flash isn't large, say, not larger then 64 MiB
>
If I just want to use the NAND /dev/mtdblock/0 as a raw device without JFFS2,
and just put a ramdisk iamge on it, how could I do? Will NTFL help in this
case?
Thanks in advance to all!
Carl Liao
next reply other threads:[~2005-04-21 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 9:28 carl liao [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-20 14:47 NAND Flash Device and JFFS2 support carl liao
2005-04-20 15:15 ` Artem B. Bityuckiy
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=Pt949578826864.08914@send1.inner-21cn.com \
--to=carlliao@21cn.com \
--cc=dedekind@infradead.org \
--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