From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
"Mukherjee, Somnath" <somnath@ti.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Gupta, Pekon" <pekon@ti.com>, "Shah, Minal" <minal.shah@ti.com>,
"Parikh, Urmil" <urmil@ti.com>
Subject: Re: MTD utils v1.5.0: MEMERASE64 ioctl failed error
Date: Sat, 12 Oct 2013 13:47:22 -0300 [thread overview]
Message-ID: <20131012164721.GA22305@localhost> (raw)
In-Reply-To: <20131011222459.GQ23337@ld-irv-0074.broadcom.com>
On Fri, Oct 11, 2013 at 03:24:59PM -0700, Brian Norris wrote:
> Hi Minal,
>
> On Wed, Oct 09, 2013 at 05:05:11AM +0000, Shah, Minal wrote:
> > I am using MTD utils version 1.5.0 for DRA7 (Vayu) platform.
> >
> > I have bad blocks in some of my NAND partitions which I am not able to erase from linux kernel.
>
> MTD does not allow erasing bad blocks. This is prohibited by NAND
> datasheets. There are occasions where, for debugging purposes, one might
> need to erase a "bad" block that is not actually bad, but MTD does not
> provide an interface for doing this. An interface for doing so was
> discussed a while back, but nothing was merged.
>
Ah, interesting. As you know I'm doing some very intrusive debugging
while developing the Armada driver and I usually need to circumvent
(manually) the kernel bad block erase check. Sometimes my blocks are not
really bad, yet they are detected as bad.
I'd be interesting in having some way to remove the check easily, but
since this is of no benefit, unless you're developing a crazy driver
I'm not sure how to do this.
What do you think?
Maybe some hidden /sys/kernel/debug/mtd file to turn that option, just
for the use of a developer?
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-12 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 5:05 MTD utils v1.5.0: MEMERASE64 ioctl failed error Shah, Minal
2013-10-11 22:24 ` Brian Norris
2013-10-12 16:47 ` Ezequiel Garcia [this message]
2013-10-15 8:32 ` Shah, Minal
2013-10-15 14:17 ` Mike Dunn
2013-10-15 16:26 ` Mike Frysinger
2013-10-15 19:12 ` Brian Norris
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=20131012164721.GA22305@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=minal.shah@ti.com \
--cc=pekon@ti.com \
--cc=somnath@ti.com \
--cc=urmil@ti.com \
--cc=vapier@gentoo.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