public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Chris Ellec <cellec@celerity.net>
To: linux-mtd@lists.infradead.org
Subject: nftl_format
Date: Thu, 06 Nov 2003 09:10:19 -0800	[thread overview]
Message-ID: <3FAA807B.30607@celerity.net> (raw)


I got an older Diskonchip with NFTL all messed up after trying to 
install Grub on it, so I had to nftl_format it.

First I had to make the changes below to get nftldump and nftl_format to 
compile again.

When I ran nftl_format, it took about 20 minutes for a 96MB DOC, is that 
normal ?

The nftl_format worked and the DOC is now back to its original state.

Chris.

-------

Please note that the following breaks the compilation of the kernel, so 
you can only do it to compile  nftl_format then you have to change it 
back if you need to recompile bzImage.

in mtd/include/linux/mtd:

--- nftl.h~    2003-10-27 15:47:40.000000000 -0800
+++ nftl.h    2003-10-28 17:18:36.000000000 -0800
@@ -8,7 +8,7 @@
 #define __MTD_NFTL_H__
 
 #include <linux/mtd/mtd.h>
-#include <linux/mtd/blktrans.h>
+//#include <linux/mtd/blktrans.h>
 
 /* Block Control Information */
 

in mtd/util:

--- Makefile~    2003-10-28 17:05:35.000000000 -0800
+++ Makefile    2003-10-28 17:06:00.000000000 -0800
@@ -10,7 +10,8 @@
 TARGETS = ftl_format erase eraseall  nanddump doc_loadbios \
     mkfs.jffs ftl_check mkfs.jffs2 lock unlock \
     einfo mtd_debug fcp nandwrite jffs2dump \
-    jffs2reader nftldump nftl_format
+    nftldump nftl_format
+    #jffs2reader
 
 SYMLINKS = crc32.h crc32.c compr_rtime.c
 

             reply	other threads:[~2003-11-06 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06 17:10 Chris Ellec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-27 22:55 nftl_format Denis Dowling
2001-04-25 19:00 nftl_format Marc Karasek

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=3FAA807B.30607@celerity.net \
    --to=cellec@celerity.net \
    --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