From: Artem Bityutskiy <dedekind@infradead.org>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: mtd-utils/flash_erase modifications
Date: Fri, 27 Oct 2006 15:39:56 +0300 [thread overview]
Message-ID: <1161952796.3080.8.camel@sauron> (raw)
In-Reply-To: <Pine.LNX.4.64.0610261052070.25906@lnxricardw.se.axis.com>
Hello Ricard,
On Fri, 2006-10-27 at 14:30 +0200, Ricard Wanderlof wrote:
> 1.
> Looking at the mtd-utils/flash_erase application (mtd-utils 1.0.1), and
> considering its use for nand flashes, there is no bad block management,
> i.e. if flash_erase hits a bad block, it exits with an error message.
> I would like to see (perhaps governed by an option) that it simply
> skips bad blocks.
Never used this utility, but granted you are saying the truth, you are
obviously right :-))
> 2.
> Furthermore, it would be nice to be able to disable the output of the
> program. As it stands, it outputs a line for each block/sector it erases.
> I would suggest a --verbose or -v option in order to enable this output.
Err, are you talking about flash_erase?
> 3.
> And finally, by default, the program only erases the first block, unless
> some options are given. If one wants to erase a whole mtd device or
> partition, the number of blocks must be known and given to flash_erase. It
> would be nice to have a default behavior, or perhaps using an option for
> backwards compatibility's sake, to simply erase the whole device.
There is flash_eraseall utility for this, isn't it? Although it may be
reasonable to have all this functionality in one utility/
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2006-10-27 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 12:30 mtd-utils/flash_erase modifications Ricard Wanderlof
2006-10-27 12:39 ` Artem Bityutskiy [this message]
2006-10-27 12:56 ` Ricard Wanderlof
2006-10-27 13:59 ` Artem Bityutskiy
2006-10-27 14:18 ` Ricard Wanderlof
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=1161952796.3080.8.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--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 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.