From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: David Peverley <pev@sketchymonkey.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: CONFIG_MTD_NAND_VERIFY_WRITE with Software ECC
Date: Fri, 25 Feb 2011 10:42:22 +0200 [thread overview]
Message-ID: <1298623342.2798.9.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.1102171013090.2784@lnxricardw.se.axis.com>
On Thu, 2011-02-17 at 11:04 +0100, Ricard Wanderlof wrote:
> Which all goes to say that as Cooke notes in his document above, it is
> necessary for the software to keep track of the number of erase cycles,
> and not just rely in the erase/write status that the chip itself reports.
Yeah, in UBI we do keep have erase counters, but we do not actually use
them to make decisions about whether to mark a block as good or bad.
Probably we should.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-02-25 8:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 12:35 CONFIG_MTD_NAND_VERIFY_WRITE with Software ECC David Peverley
2011-02-15 13:02 ` Ricard Wanderlof
2011-02-15 14:00 ` David Peverley
2011-02-15 15:01 ` Ricard Wanderlof
2011-02-15 17:58 ` David Peverley
2011-02-17 10:04 ` Ricard Wanderlof
2011-02-25 8:42 ` Artem Bityutskiy [this message]
2011-02-25 9:09 ` Ricard Wanderlof
2011-02-25 10:29 ` Artem Bityutskiy
2011-02-25 11:36 ` Ivan Djelic
2011-02-25 12:12 ` Artem Bityutskiy
2011-02-25 12:59 ` David Peverley
2011-02-25 13:21 ` Artem Bityutskiy
2011-02-25 18:27 ` Ivan Djelic
2011-02-25 14:44 ` Ivan Djelic
2011-02-25 16:41 ` Artem Bityutskiy
2011-02-25 12:22 ` Artem Bityutskiy
2011-02-25 15:14 ` Ivan Djelic
2011-02-25 8:31 ` Artem 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=1298623342.2798.9.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pev@sketchymonkey.com \
--cc=ricard.wanderlof@axis.com \
/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