From: Bill Roman <roman@alerton.com>
To: MTD <mtd@infradead.org>
Subject: Re: Questions about MTD
Date: Mon, 20 Mar 2000 10:06:37 -0800 [thread overview]
Message-ID: <38D668AD.BBB356B2@alerton.com> (raw)
In-Reply-To: E12WPTl-0007TN-00@infradead.org
Dvir Oren wrote:
>
> 3. erase seg faults. Is erase supposed to do what docpmap /e
> does?
You can supply a block number on the command line, and/or apply this patch:
diff -ur mtd-20000131.orig/util/erase.c mtd-20000131/util/erase.c
--- mtd-20000131.orig/util/erase.c Tue Aug 17 15:57:08 1999
+++ mtd-20000131/util/erase.c Wed Feb 23 10:23:19 2000
@@ -35,7 +35,7 @@
erase.length = meminfo.erasesize;
printf("Erasesize 0x%lx\n", meminfo.erasesize);
- if (argc >= 2)
+ if (argc > 2)
erase.start = atoi(argv[2]);
else
erase.start = 0;
Also, if you'd like nftl_format not to print gibberish for a usage message:
diff -ur mtd-20000131.orig/util/nftl_format.c mtd-20000131/util/nftl_format.c
--- mtd-20000131.orig/util/nftl_format.c Fri Aug 20 08:31:01 1999
+++ mtd-20000131/util/nftl_format.c Wed Feb 16 11:45:10 2000
@@ -107,7 +107,8 @@
struct mtd_oob_buf oob = {0, 16, oobbuf};
if (argc < 2) {
- fprintf(stderr,"Usage: %s <mtddevice> [<start offset> [<size>]]\n");
+ fprintf(stderr,"Usage: %s <mtddevice> [<start offset> [<size>]]\n",
+ argv[0]);
return 1;
}
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-03-20 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-18 20:05 Questions about MTD Dvir Oren
2000-03-20 9:41 ` David Woodhouse
2000-03-20 18:06 ` Bill Roman [this message]
2000-03-20 18:49 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2000-03-20 11:17 Oron Ogdan
2000-03-20 13:51 ` Kyle Harris
2000-03-20 14:11 Oron Ogdan
2000-03-20 16:17 ` Kyle Harris
2000-03-20 19:34 Dvir Oren
2000-03-21 9:01 ` David Woodhouse
2000-03-20 20:51 Oron Ogdan
2000-03-21 2:59 ` Kyle Harris
2000-03-20 20:51 Oron Ogdan
2000-03-21 12:36 Oron Ogdan
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=38D668AD.BBB356B2@alerton.com \
--to=roman@alerton.com \
--cc=mtd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox