From: "Edward J. Lee" <noshel@idis.co.kr>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: A question on ECC
Date: Tue, 15 Apr 2003 02:40:05 +0900 [thread overview]
Message-ID: <3E9AF275.4000905@idis.co.kr> (raw)
In-Reply-To: <200304140954.27049.tglx@linutronix.de>
Thomas Gleixner wrote:
>On Monday 14 April 2003 07:13, Edward Lee (???) wrote:
>
>
>>Hi Earl, thanks for the help.
>>
>>I didn't use nandwrite, I wrote on the chip using plain stuff like 'cp' or
>>'tar', etc. (having a file system on my device, I couldn't find a reason
>>to write files using other programs)
>>
>>
>nandwrite is just used to copy a filesystem image to a unformatted chip.
>If you have mounted the fs already, then nandwrite would be the wrong tool.
>
>These messages have a different reason. I assume that you followed the advice
>on yaffs list and you have enabled YAFFS_USE_NANDECC and disabled
>YAFFS_USE_OLD_MTD.
>
>Then I can only guess, that you did not select a ecc mode in your board driver
>code.
>
><SNIP>
> /* 20 us command delay time */
> this->chip_delay = 20;
> this->eccmode = NAND_ECC_SOFT;
><SNIP>
>
>NAND_ECC_SOFT is the right choice, if you don't have a hardware ecc generator.
>If you have one, you must supply the neccecary functions to use it.
>
>
>
this->eccmode is indeed set to NAND_ECC_SOFT.
I guess my case is kind of 'extra-tricky'. I just found out another
weird thing,
that the warning messages complaining '...without ECC...' do NOT appear when
I'm 'writing' on the chip. Strange, eh. :'(
next prev parent reply other threads:[~2003-04-14 8:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 0:18 A question on ECC Edward Lee \(이장원\)
2003-04-14 2:01 ` Earl Manning
2003-04-14 5:13 ` Edward Lee (???)
2003-04-14 7:54 ` Thomas Gleixner
2003-04-14 17:40 ` Edward J. Lee [this message]
2003-04-14 10:03 ` Gerhard Uttenthaler
2003-04-14 11:17 ` Thomas Gleixner
2003-04-14 11:25 ` Thomas Gleixner
2003-04-18 9:47 ` Edward J. Lee
2003-04-18 8:49 ` Thomas Gleixner
2003-04-19 4:14 ` Edward Lee (???)
2003-04-19 7:31 ` Thomas Gleixner
2003-04-14 14:06 ` Earl Manning
2003-04-14 15:26 ` Thomas Gleixner
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=3E9AF275.4000905@idis.co.kr \
--to=noshel@idis.co.kr \
--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 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.