From: Artem Bityutskiy <dedekind1@gmail.com>
To: Stephen Beaver <beavers@anx.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Mtd_debug patch
Date: Sun, 13 Jun 2010 11:57:49 +0300 [thread overview]
Message-ID: <1276419469.19028.176.camel@localhost> (raw)
In-Reply-To: <C825AD54.2A59A%beavers@anx.com>
Hi Stephen,
On Fri, 2010-05-28 at 17:26 -0400, Stephen Beaver wrote:
> The attached patch to the current version of mtd_debug (grabbed
> on5/28/2010) adds two new capabilities:
>
> usage: mtd_debug info <device>
> mtd_debug read <device> <offset> <len> <dest-filename>
> mtd_debug write <device> <offset> <len> <source-filename>
> mtd_debug verify <device> <offset> <cmp-filename>
> mtd_debug erase <device> <offset> <len>
> mtd_debug blank <device> <offset> <len>
>
> mtd_debug blank ... checks that an area of flash memory if blank (all
> 0xFFs) ie it verifies that an erase succeeded.
> mtd_debug verify ... checks that the contents of the flash memory
> match the specified file. Ie it verifies that a write succeeded.
>
> These functions allow things like:
>
> #!/bin/sh
>
> mtd_debug erase /dev/mtd1 0 0x200000
> mtd_debug write /dev/mtd1 0 0x150000 uImage
> if ( mtd_debug verifiy /dev/mtd1 0 uImage ) ; then
> reboot
> else
> # Better try again, or we will die
> fi
Looks like a useful feature, but I cannot apply your patch because it is
not applicable to the latest mtd-utils.git. Also, your patch has many
trailing white-spaces. Could you please re-send it in inlined form - it
will make it easier to review it and reply to you (it it difficult to
comment attached patches).
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-06-13 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 21:26 Mtd_debug patch Stephen Beaver
2010-06-13 8:57 ` Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-28 2:41 mtd debug patch 斗破苍穷
2011-07-28 3:26 ` Jean-Christophe PLAGNIOL-VILLARD
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=1276419469.19028.176.camel@localhost \
--to=dedekind1@gmail.com \
--cc=beavers@anx.com \
--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.