public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Lorenzo PARISI <lorenzo.parisi@st.com>
Cc: MTD mailing list <linux-mtd@lists.infradead.org>,
	YAFFS mailing list <yaffs@stoneboat.aleph1.co.uk>
Subject: Re: Benchmark errors
Date: Fri, 08 Oct 2004 12:27:44 +0200	[thread overview]
Message-ID: <1097231263.11402.1449.camel@thomas> (raw)
In-Reply-To: <1097229657.11402.1440.camel@thomas>

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

On Fri, 2004-10-08 at 12:00, Thomas Gleixner wrote:
> On Fri, 2004-10-08 at 11:52, Lorenzo PARISI wrote:
> > Hi all,
> > nand_write_oob: Failed write verify, page 0x0....
> 
> So it works with JFFS2 and it fails on YAFFS. The MTD internal interface
> was reworked some time ago and it might be that the write verify does
> not work with YAFFS anymore, as YAFFS is using a legacy variant of the
> interface. Can you please switch of the write verify and test again ?
> 
Can you please figure out, where the verify exactly fails ?
Please apply the attached patch to nand_base.c

tglx



[-- Attachment #2: nand_base.diff --]
[-- Type: text/x-patch, Size: 890 bytes --]

diff -u -r1.121 nand_base.c
--- nand_base.c	6 Oct 2004 19:53:11 -0000	1.121
+++ nand_base.c	8 Oct 2004 10:34:39 -0000
@@ -310,11 +310,17 @@
 {
 	int i;
 	struct nand_chip *this = mtd->priv;
+	u_char tmp;
 
-	for (i=0; i<len; i++)
-		if (buf[i] != readb(this->IO_ADDR_R))
+	for (i=0; i<len; i++) {
+		tmp = readb(this->IO_ADDR_R);
+		if (buf[i] != tmp) {
+			DEBUG (MTD_DEBUG_LEVEL0, 
+			       "Verify failed: 0x%02x instead of 0x%02x at offset %d\n",
+			       tmp, buf[i], i);
 			return -EFAULT;
-
+		}
+	}
 	return 0;
 }
 
@@ -955,7 +961,7 @@
 		 */
 		if (oobmode) {
 			if (this->verify_buf(mtd, &oob_buf[oobofs], mtd->oobsize - hweccbytes * eccsteps)) {
-				DEBUG (MTD_DEBUG_LEVEL0, "%s: " "Failed write verify, page 0x%08x ", __FUNCTION__, page);
+				DEBUG (MTD_DEBUG_LEVEL0, "%s: " "Failed write verify oob, page 0x%08x ", __FUNCTION__, page);
 				goto out;
 			}
 		} else {

      reply	other threads:[~2004-10-08 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08  9:52 Benchmark errors Lorenzo PARISI
2004-10-08 10:00 ` Ben Dooks
2004-10-08 10:00 ` Thomas Gleixner
2004-10-08 10:27   ` Thomas Gleixner [this message]

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=1097231263.11402.1449.camel@thomas \
    --to=tglx@linutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lorenzo.parisi@st.com \
    --cc=yaffs@stoneboat.aleph1.co.uk \
    /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