From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org
Cc: Siddharth Choudhuri <choudhri@cs.tamu.edu>
Subject: Re: Multiple writes to NAND OOB...
Date: Fri, 22 Sep 2006 15:18:46 +1200 [thread overview]
Message-ID: <200609221518.46412.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <Pine.GSO.4.58.0609201121180.26525@sun>
On Thursday 21 September 2006 04:30, Siddharth Choudhuri wrote:
> Hi,
>
> I have the following question regarding multiple writes to OOB data:
>
> Is it possible to write to the OOB data of the same page multiple times ?
Yes it is **possible**, but be be careful. If you do too many writes without
an erase you can cause corruptions due to "write disturb".
> If so, does it mean that the bytes being written are to different
> locations(offsets) of the OOB because a byte cannot be rewritten in NAND
> unless its block is erased ?
If you write to NAND, then what you get is the ANDing of the pattern you write
against what was already there.
If a byte had 0011-0101 and you program 1101-0011 nto it you'll end up with
0001-0001.
Thus, if you want to program a new pattern into some bytes, you use 0xff for
any bytes you don't want to change.
You need to do an erase to change bits back to 1.
Note a subtle difference. Most NOR writes will fail if you write a pattern
that tries to set a bit from 0 to a 1. On NAND, the bit will not change, but
it is not an error to try to do this.
-- CHarles
prev parent reply other threads:[~2006-09-22 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 16:30 Multiple writes to NAND OOB Siddharth Choudhuri
2006-09-22 3:18 ` Charles Manning [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=200609221518.46412.manningc2@actrix.gen.nz \
--to=manningc2@actrix.gen.nz \
--cc=choudhri@cs.tamu.edu \
--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