public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Alex Samoutin <samoutin@hotbox.ru>, linux-mtd@lists.infradead.org
Subject: Re: NAND subsector writing problem
Date: Fri, 31 Jan 2003 08:10:31 +0100	[thread overview]
Message-ID: <200301310810.31301.tglx@linutronix.de> (raw)
In-Reply-To: <004701c2c8ce$107caea0$1a00a8c0@itc.intrinsyc.com>

On Friday 31 January 2003 03:11, Alex Samoutin wrote:
>  don't know much about sub-page writing. I've only took latest MTD snapshot
> and wrote hardware level driver for NAND chip on IBM 405ep board. And then
> started "nandtest" program from the same snapshot. So, if "mixing ECC and
> sub-page writes is invalid" then something wrong in "nand.c" or "nandtest.o"
nandtest is not a valid testprogram for NAND. It should be removed from CVS.

> And furthermore -  that was not ECC error, it was error during verify read
> after write (read and write buffer not match).
> Also I have troubles with JFFS2  :(.  nand_write_page failed after verify
> ( If CONFIG_MTD_NAND_VERIFY_WRITE not defined - I have no error message)
Can you turn NAND debugging on and send me the debug output ?

-- 
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  parent reply	other threads:[~2003-01-31  6:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-30  1:10 NAND subsector writing problem Alex Samoutin
2003-01-30  8:23 ` David Woodhouse
2003-01-30 20:57 ` Charles Manning
2003-01-31  2:11   ` Alex Samoutin
2003-01-31  4:01     ` Charles Manning
2003-01-31  7:10     ` Thomas Gleixner [this message]
2003-02-01  2:10       ` Alex Samoutin

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=200301310810.31301.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=samoutin@hotbox.ru \
    /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