public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Markus Schiltknecht <markus@bluegap.ch>
Cc: linux-mtd@lists.infradead.org
Subject: Re: curious questions
Date: Wed, 21 May 2008 11:38:27 +0200	[thread overview]
Message-ID: <20080521093827.GB20358@logfs.org> (raw)
In-Reply-To: <4833E87D.10209@bluegap.ch>

On Wed, 21 May 2008 11:16:45 +0200, Markus Schiltknecht wrote:
> 
> Am I understanding correctly, that I can't write to the a single page 
> with MTD (after having erased the according erase-block)? Even if I'm 
> writing the single pages in the block sequentially?

You can erase no less than one erase-block.  For NAND, you cannot easily
write less than one page.  Sometimes subpage writes work, sometimes they
don't, they have strange limitations and are best ignored in the
beginning.

> Can I repeatedly write to a NAND flash page, to set its bits to 1 
> (without resetting any bit to 0) (or vice-versa for XOR)?

Erase sets bits to 1, writes sets them to 0.

With old NOR flashes, you can repeatedly write the same area to flip
single bits.  Writes with all 1's are essentially noops, so to set a
single bit write a word will all but one bit set to 1.  With ECC you'd
have to flip bits on the ECC backwards, which doesn't work.  NAND has
ECC, so ordinarily this trick won't work.

Theoretically you could still use it, since ECC can be done in software
- using any algorithm you like including none.  But practically many
chips seem to misbehave if you violate the spec and repeatedly write to
the same area.  So don't.

Jörn

-- 
People will accept your ideas much more readily if you tell them
that Benjamin Franklin said it first.
-- unknown

  reply	other threads:[~2008-05-21  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  9:16 curious questions Markus Schiltknecht
2008-05-21  9:38 ` Jörn Engel [this message]
2008-05-21  9:52   ` Markus Schiltknecht
2008-05-21 10:01     ` Jörn Engel

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=20080521093827.GB20358@logfs.org \
    --to=joern@logfs.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=markus@bluegap.ch \
    /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