From: "\"David Müller (ELSOFT AG)\"" <d.mueller@elsoft.ch>
To: linux-mtd@lists.infradead.org
Subject: Re: word line disturbance
Date: Wed, 15 Oct 2003 09:20:14 +0200 [thread overview]
Message-ID: <3F8CF52E.1050502@elsoft.ch> (raw)
In-Reply-To: <3C6BEE8B5E1BAC42905A93F13004E8AB03202232@mailse01.axis.se>
Hello
Magnus Mårtensson wrote:
> Hi.
> I had a discussion with flash manufacturer Atmel last week regarding a phenomenon that we had seen.
> The phenomenon was called "word line disturbance" and it could occur if you tried to program only ones
> to a location that already contained ones. The result could be that some bit on another address got tainted. Ex
> writing 0xffff to address A could result in the content on address B changing from 0xffff to 0xfffe.
>
Does anybody know more about the technical background of this "it's not
a bug, it's a feature" problem? Or is it just a manager driven decision
to save some money at the wrong place?
Dave
next prev parent reply other threads:[~2003-10-15 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 15:31 word line disturbance Magnus Mårtensson
2003-10-14 15:46 ` Steven Scholz
2003-10-14 17:31 ` Thayne Harbaugh
2003-10-14 21:39 ` Charles Manning
2003-10-15 7:20 ` "David Müller (ELSOFT AG)" [this message]
2003-10-16 19:34 ` Charles Manning
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=3F8CF52E.1050502@elsoft.ch \
--to=d.mueller@elsoft.ch \
--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