From: schang@3inet.com (Shuh C Chang)
To: "Felix Radensky" <felix@allot.com>,
"Linux-mtd" <linux-mtd@lists.infradead.org>
Subject: Re: DOC problems on PowerPC
Date: Mon, 14 May 2001 09:36:49 -0500 [thread overview]
Message-ID: <003b01c0dc83$4f6ace00$88b4b8d1@ShuhIII> (raw)
In-Reply-To: 3AFFE80B.DCE1B139@allot.com
> All I had to do is to run "eraseall /dev/mtd0",
Is "eraseall" equivalent to the DOS utility "docpmap /e" in functionality?
Anyone who can shed some light?
Shuh Chang
----- Original Message -----
From: "Felix Radensky" <felix@allot.com>
To: "Linux-mtd" <linux-mtd@lists.infradead.org>
Sent: Monday, May 14, 2001 9:13 AM
Subject: DOC problems on PowerPC
> Hi, all
>
> I was able to solve the DOC problems on PowerPC I've reported yesterday.
>
> All I had to do is to run "eraseall /dev/mtd0", then run "nftl_format
> /dev/mtd0"
> and then create partitions with fdisk.
>
> Can someone please explain me the difference between eraseall and
> nftl_format.
> HOWTO says nothing about it.
>
> By the way, the latest mtd code would not compile, at least on my 2.4.2
> kernel
> unless you add #include <linux/kmod.h> to chipreg.c. This is because of
>
> a call to request_module() in do_map_probe(), which IMHO should be
> under #ifdef CONFIG_KMOD, and not #ifdef CONFIG_MODULES.
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2001-05-14 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 14:13 DOC problems on PowerPC Felix Radensky
2001-05-14 14:36 ` Shuh C Chang [this message]
2001-05-16 0:34 ` Ollie Lho
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='003b01c0dc83$4f6ace00$88b4b8d1@ShuhIII' \
--to=schang@3inet.com \
--cc=felix@allot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox