public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Steven Hein <ssh@sgi.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Integrating new MTD/jffs2 into 2.4.18 kernel
Date: Thu, 25 Jul 2002 10:45:34 -0500	[thread overview]
Message-ID: <3D401D1E.2DD54BF@sgi.com> (raw)
In-Reply-To: 600.1027603720@redhat.com

David, Joern,

Thanks for the help!  My jffs2 filesystem is now working in NAND flash!

For the benefit of others, here's a summary of what I needed to do
to get this going.

Here's generally what I needed to do.

1) apply the patch ftp://ftp.kernel.org/pub/linux/kernel/people/dwmw2/shared-zliblinux-2.4.19-pre10-shared-zlib.bz2 

   NOTE: I am running linux-2.4.18 + linux-2.4.18-rmk7 ARM patch,
         which already contains some parts of the above patch. So, I had
         to go through the patch and grab the parts I needed.  If this
         is the case for you.....

      a) copy CVS:mtd/lib/zlib_inflate and CVS:mtd/lib/zlib_deflate
         to linux/lib
      b) modify linux/lib Makefile as indicated in the above patch
      c) remove linux/fs/inflate_fs
      e) modify linux/fs/Makefile and linux/fs/cramfs/uncompress.c
         as indicated in the above patch
      f) add the line "source lib/Config.in" to arch/<yours>/Config.in
         (as is done in the above patch)
      *) I think that's all I needed....basically I went through the above
         patch and applied everything in it by hand.

2) remove linux/fs/jffs2

3) copy CVS:mtd/fs/jffs2 to linux/fs/jffs2

4) copy fs/jffs2/crc32.h to linux/include/linux/crc32.h

5) in linux/fs/jffs2/file.c, there is a reference to PageUptodate()
   that must be changed to Page_Uptodate()   (looks like this syntax
   changed from 2.4 to 2.5 kernel....)

6) apply the following patch to linux/fs/Config.in:

diff -uNr linux/fs/Config.in linux.new_jffs2/fs/Config.in
--- linux/fs/Config.in  Mon Feb 25 13:38:07 2002
+++ linux.new_jffs2/fs/Config.in        Thu Jul 25 10:05:41 2002
@@ -42,6 +42,7 @@
 dep_tristate 'Journalling Flash File System v2 (JFFS2) support' CONFIG_JFFS2_FS $CONFIG_MTD
 if [ "$CONFIG_JFFS2_FS" = "y" -o "$CONFIG_JFFS2_FS" = "m" ] ; then
    int 'JFFS2 debugging verbosity (0 = quiet, 2 = noisy)' CONFIG_JFFS2_FS_DEBUG 0
+   dep_bool '  JFFS2 support for NAND flash (EXPERIMENTAL)' CONFIG_JFFS2_FS_NAND $CONFIG_EXPERIMENTAL
 fi
 tristate 'Compressed ROM file system support' CONFIG_CRAMFS
 bool 'Virtual memory file system support (former shm fs)' CONFIG_TMPFS



Once I did that, I had a working, writable JFFS2 filesystem running
on NAND flash.

Thanks again for the help!!

Steve






David Woodhouse wrote:
> 
> joern@wohnheim.fh-wedel.de said:
> >  My guess is that you need the zlib stuff in the kernel lib, you
> > should have linux/lib/zlib_inflate and linux/lib/zlib_deflate in your
> > source plus some modifications in arch/<yours>/config.in, lib/Makefile
> > and include/linux/zlib.h. Roughly.
> 
> ftp://ftp.??.kernel.org/pub/linux/kernel/people/dwmw2/shared-zlib/linux-2.4.19-pre10-shared-zlib.bz2
> 
> And I think you may need to copy fs/jffs2/crc32.h to include/linux/crc32.h
> or something similar.
> 
> --
> dwmw2
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Hein (ssh@sgi.com)              Engineering Diagnostics/Software
Silicon Graphics, Inc.                          
1168 Industrial Blvd.                 Phone: (715) 726-8410
Chippewa Falls, WI 54729              Fax:   (715) 726-6715
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  reply	other threads:[~2002-07-25 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25 12:25 Integrating new MTD/jffs2 into 2.4.18 kernel Steven Hein
2002-07-25 13:14 ` Jörn Engel
2002-07-25 13:28   ` David Woodhouse
2002-07-25 15:45     ` Steven Hein [this message]
2002-07-25 16:35       ` David Woodhouse

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=3D401D1E.2DD54BF@sgi.com \
    --to=ssh@sgi.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