All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Ferenc Havasi <havasi@inf.u-szeged.hu>
Cc: linux-mtd@lists.infradead.org, "Zhao, Forrest" <forrest.zhao@intel.com>
Subject: Re: The problem that I didn't think out
Date: Mon, 28 Nov 2005 13:15:27 +0300	[thread overview]
Message-ID: <438AD8BF.8020905@yandex.ru> (raw)
In-Reply-To: <438A5023.4040503@inf.u-szeged.hu>

Ferenc Havasi wrote:
> Be that as it may I have a NAND question, I think you know the answer 
> (NAND Guru Artem :) ):
> - if there is and erase block aready fulled, is there any possibility to 
> mark its pages as obsolated (individually)? Is it allowed to write to 
> OOB (or data) area one more? (or write OOB later than the data... or 
> similar trick?)

Yes, but this depends on NAND type. In the worst case, you may write at 
least once there. In case of some NANDs - more.

Note, JFFS2 writes clean marker to OOB area of the first page of a newly 
erased eraseblock. But it doesn't prohibit JFFS2 to write to this page 
later, and store ECC in OOB, even though this OOB already contains some 
data (the clean marker).


-- 
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.

  reply	other threads:[~2005-11-28 10:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-25  8:36 The problem that I didn't think out Zhao, Forrest
2005-11-25 11:58 ` Artem B. Bityutskiy
2005-11-27 13:01   ` Ferenc Havasi
2005-11-27 13:20     ` Artem B. Bityutskiy
2005-11-28  0:32       ` Ferenc Havasi
2005-11-28 10:15         ` Artem B. Bityutskiy [this message]
2005-11-28  2:20   ` zhao, forrest
2005-11-28 10:24     ` Artem B. Bityutskiy

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=438AD8BF.8020905@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=forrest.zhao@intel.com \
    --cc=havasi@inf.u-szeged.hu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.