From: Michael <xemc@yahoo.com>
To: "David A. Marlin" <dmarlin@redhat.com>
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: NAND fail testing
Date: Thu, 13 Jan 2005 10:12:58 -0800 (PST) [thread overview]
Message-ID: <20050113181258.13116.qmail@web52701.mail.yahoo.com> (raw)
In-Reply-To: <41E699F9.10704@redhat.com>
>
> Is there a simple way (using existing drivers and utilities) to
> "wear out" one byte on a NAND type chip by repeatedly rewriting a
> single byte (single address)?
As I understand, you can write over an already-written page with
new values. Could you continually write the same data to a page,
except for the byte that you want to wear out?
I think because of the way NAND works, with a 512 byte buffer that
goes all at once into NAND that you can't do much other than
something like this.
Mike
prev parent reply other threads:[~2005-01-13 18:13 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
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 [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=20050113181258.13116.qmail@web52701.mail.yahoo.com \
--to=xemc@yahoo.com \
--cc=dmarlin@redhat.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