public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "David A. Marlin" <dmarlin@redhat.com>
To: tglx@linutronix.de
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: NAND fail testing
Date: Thu, 13 Jan 2005 11:56:07 -0600	[thread overview]
Message-ID: <41E6B637.9070202@redhat.com> (raw)
In-Reply-To: <1105638483.5993.2.camel@lap02.tec.linutronix.de>


Thomas Gleixner wrote:

> 
> We have blocked the access to short writes. You can do the following:
> 
> Erase a block from userspace with flash_erase
> Write a page of all 0xff except one byte to the first page using
> nandwrite
> 
> Repeat until you get an error

Would this not still 'write' all bytes in the page (even though they are 
0xff and unchanged), causing them to also wear and possibly fail?


d.marlin

  reply	other threads:[~2005-01-13 17:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13 15:55 NAND fail testing David A. Marlin
2005-01-13 17:48 ` Thomas Gleixner
2005-01-13 17:56   ` David A. Marlin [this message]
2005-01-13 18:15     ` Thomas Gleixner
2005-01-13 18:24       ` Artem B. Bityuckiy
2005-01-13 17:52 ` Charles Manning
2005-01-13 18:11   ` David A. Marlin
2005-01-13 18:12 ` Michael

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=41E6B637.9070202@redhat.com \
    --to=dmarlin@redhat.com \
    --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