From: "Edward Lee \(???\)" <noshel@idis.co.kr>
To: "Earl Manning" <EManning@PRISMIQ.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: A question on ECC
Date: Mon, 14 Apr 2003 14:13:20 +0900 [thread overview]
Message-ID: <000501c30244$91a09dc0$525deecb@noshel> (raw)
In-Reply-To: 20030413210133.64cc28b9.EManning@PRISMIQ.com
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)
----- Original Message -----
From: "Earl Manning" <EManning@PRISMIQ.com>
To: <linux-mtd@lists.infradead.org>
Sent: Monday, April 14, 2003 11:01 AM
Subject: Re: A question on ECC
Hi Edward,
I am using a similar chip with JFFS2. When you wrote the image, did you use the supplied utility 'nandwrite'? If you did, did you invoke it with the "--yaffs" option?
I hope this helps,
Earl Manning
On Mon, 14 Apr 2003 09:18:09 +0900
Edward Lee \(ÀÌÀå¿ø\) <noshel@idis.co.kr> wrote:
> Hello. I'm Edward Lee in Korea.
>
> I'm using samsung NAND flash, with YAFFS on it..
> But I'm having problems with ECC.
> I wrote a file that's needed to use the flash chip with my board,
> and here's a small part of code that defines the partitions.
>
> static struct mtd_partition partition_info[] = {
> { name: "a",
> offset: 0,
> size: 32 * 512 },
> { name: "b",
> offset: 16384,
> size: 2 * 1024 * 1024 },
> { name: "c",
> offset: 2113536,
> size: 2 * 1024 * 1024 },
> { name: "d",
> offset: 4210688,
> size: 11 * 1024 * 1024 },
> { name: "e",
> offset: 15745024,
> size: 1032192 }
> };
> #define NUM_PARTITIONS 5
>
> I'm using YAFFS on partitions "d" and "e".
> But I can't stop recieving annoying kernel messages saying
> "Reading data from NAND FLASH without ECC is not recommended".
>
> On YAFFS's side, I set the option CONFIG_YAFFS_USE_NANDECC,
> which I believe that asks the mtd NAND to do the ECC.
> So, I would like to ask if any other settings are necessary in order to enable ECC.
> (Probably something should be added to the stuff above?)
>
> Well, that's all, and thanks for the great work.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2003-04-14 5:13 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 (???) [this message]
2003-04-14 7:54 ` Thomas Gleixner
2003-04-14 17:40 ` Edward J. Lee
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='000501c30244$91a09dc0$525deecb@noshel' \
--to=noshel@idis.co.kr \
--cc=EManning@PRISMIQ.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox