From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jon Povey <Jon.Povey@racelogic.co.uk>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Mike Frysinger <vapier.adi@gmail.com>
Subject: RE: linux equivalent of u-boot's "nand scrub" (erasing blocks even whenOOB says "bad")
Date: Mon, 13 Sep 2010 09:25:40 +0300 [thread overview]
Message-ID: <1284359140.27765.156.camel@localhost> (raw)
In-Reply-To: <70E876B0EA86DD4BAF101844BC814DFE0903E3E3DD@Cloud.RL.local>
On Mon, 2010-09-13 at 06:54 +0100, Jon Povey wrote:
> Mike Frysinger wrote:
> > ive come across a situation where it would have been invaluable to
> > have the ability to "scrub" the nand flash while running linux.
>
> I would find this useful too, or more specifically I recently wanted to rewrite the BBT in software from linux (to change OOB layout), but those blocks are marked off-limits. Some way to force it would be nice.
>
> I am just rambling though, no real useful suggestion :) Sorry..
>
> As for clearing blocks marked bad, how about MEMSETGOODBLOCK as the inverse of the existing MEMSETBADBLOCK?
So may be we need a separate ioctl for dealing with bad eraseblocks
which will also include abilities to re-write BBT?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-09-13 6:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 23:53 linux equivalent of u-boot's "nand scrub" (erasing blocks even when OOB says "bad") Mike Frysinger
2010-09-11 6:32 ` Artem Bityutskiy
2010-09-12 4:03 ` Mike Frysinger
2010-09-12 7:54 ` Artem Bityutskiy
2010-09-22 7:43 ` Mike Frysinger
2010-09-23 12:28 ` Artem Bityutskiy
2010-09-23 19:55 ` Mike Frysinger
2010-09-24 8:47 ` Artem Bityutskiy
2010-09-13 5:54 ` linux equivalent of u-boot's "nand scrub" (erasing blocks even whenOOB " Jon Povey
2010-09-13 6:25 ` Artem Bityutskiy [this message]
2010-09-14 1:16 ` Mike Frysinger
2010-09-14 1:53 ` Jon Povey
2010-09-14 1:59 ` Mike Frysinger
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=1284359140.27765.156.camel@localhost \
--to=dedekind1@gmail.com \
--cc=Jon.Povey@racelogic.co.uk \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.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;
as well as URLs for NNTP newsgroup(s).