From: "Steve Tsai" <startec@ms11.hinet.net>
To: "'Thomas Gleixner'" <tglx@linutronix.de>
Cc: "Linux MTD mailing list" <linux-mtd@lists.infradead.org>
Subject: RE: NAND Configuration
Date: Tue, 6 Aug 2002 18:40:32 +0800 [thread overview]
Message-ID: <001c01c23d35$b0e899f0$5501a8c0@synso.com.tw> (raw)
In-Reply-To: <1028624857.19435.2.camel@thomas.tec.linutronix.de>
-----Original Message-----
From: linux-mtd-admin@lists.infradead.org
[mailto:linux-mtd-admin@lists.infradead.org] On Behalf Of Thomas
Gleixner
Sent: Tuesday, August 06, 2002 5:08 PM
To: Steve Tsai
Cc: Linux MTD mailing list
Subject: Re: NAND Configuration
On Tue, 2002-08-06 at 09:25, Steve Tsai wrote:
> Does I have to set CONFIG_MTD_NAND_ECC_JFFS2=y and
> CONFIG_JFFS2_FS_NAND=y to use NAND flash? Weh I set these settings, I
> will get the following easily. If I did not set these settings and
> the condition is better, still has problem, but it will not halt the
> system. If I need not set CONFIG_MTD_NAND_ECC_JFFS2=y and
> CONFIG_JFFS2_FS_NAND=y, I can trace my problem easily. I use
> mtd-snapshot-20020731.tar.bz2 with uClinux.
You have to set it. Read http://linux-mtd.infradead.org/tech/nand.html
I read it many time, but CONFIG_JFFS2_FS_NAND use to take care buffering
and OOB . Does I have to use it absolutely? If I do not use it, what's
the result of the driver?
>
> ARGH. About to write node to 0x0018de8c on flash, but there are data
> already the
> re:
> 0x0018de8c: 85 19 04 20 74 01 00 00 4d 62 52 56 ff ff ff ff pid 24:
> failed 256
>
> jffs2_flush_wbuf(): Write failed with -5
> Write of 68 bytes at 0x004da000 failed. returned -5, retlen 0 Not
> marking the space at 0x004da000 as dirty because the flash driver
> returned r etlen zero
We need more info from mount onwards.
Maybe I do not provide repeatable messages and steps. The following are
the steps I use.
1. eraseall /dev/mtd1
2. mount -t jffs2 /dev/mtdblock1 /mnt
3. Make directory to /mnt
4. Use ftp to copy files to /mnt
5. Change the kernel to to mount /dev/mtdblock1 as root FS.
6. Copy or delete files and sometime the message display
ARGH. About to write node to 0x003f9e2c on flash, but there are
data already the re:...
After that, the patition will display more error messages, ECC error
and others.
Regards,
Steve tsai
next prev parent reply other threads:[~2002-08-06 10:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 7:25 NAND Configuration Steve Tsai
2002-08-06 9:07 ` Thomas Gleixner
2002-08-06 10:40 ` Steve Tsai [this message]
2002-08-06 12:16 ` Thomas Gleixner
2002-08-07 9:08 ` Steve Tsai
2002-08-07 10:05 ` David Woodhouse
2002-08-07 10:19 ` Steve Tsai
2002-08-07 10:49 ` Thomas Gleixner
2002-08-07 21:11 ` Alice Hennessy
2002-08-08 8:59 ` Thomas Gleixner
2002-08-08 9:14 ` David Woodhouse
2002-08-08 9:28 ` Thomas Gleixner
2002-08-08 2:47 ` Steve Tsai
2002-08-08 5:23 ` Steve Tsai
2002-08-08 9:11 ` Thomas Gleixner
2002-08-08 9:37 ` Steve Tsai
2002-08-08 11:05 ` David Woodhouse
2002-08-09 6:53 ` Steve Tsai
2002-08-09 8:09 ` Thomas Gleixner
2002-08-10 7:54 ` Steve Tsai
2002-08-10 8:41 ` Thomas Gleixner
2002-08-12 6:30 ` Steve Tsai
2002-08-06 9:45 ` Thomas Gleixner
2002-08-06 10:25 ` Steve Tsai
2002-08-06 12:28 ` Thomas Gleixner
2002-08-06 12:32 ` David Woodhouse
2002-08-06 12:40 ` Thomas Gleixner
2002-08-07 10:45 ` Steve Tsai
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='001c01c23d35$b0e899f0$5501a8c0@synso.com.tw' \
--to=startec@ms11.hinet.net \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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