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: Integrating new MTD/jffs2 into 2.4.18 kernel
Date: Thu, 25 Jul 2002 07:25:08 -0500	[thread overview]
Message-ID: <3D3FEE24.49D26D61@sgi.com> (raw)

Hello,

I am running on an ARM platform using the 2.4.18 kernel with 2.4.18-rmk7
patch.  I'm using the MTD NAND flash support, and I'm having problems
running a jffs2 filesystem on a NAND flash device  (not a root
filesystem,
just a writable "scratch" directory).

Using a snapshot from yesterday, I tried to integrate the jffs2 from
the snapshot into my kernel.  But there were a few issues:
- include/linux/crc32.h but expected by the files in fs/jffs2
- zlib.[ch] were not in the jffs2 dir as they were previously

I tried fixing these, but still ended up missing the zlib_deflate*
functions.....

So my question is:   is there a place I can grab the MTD/jffs2 stuff
to drop directly into a 2.4.18-rmk7 kernel?   Or, is there a
procedure somewhere describing how to integrate the latest MTD
from CVS (especially jffs2) into the latest 2.4.x kernel?

Thanks in advance!

Steve


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25 12:25 Steven Hein [this message]
2002-07-25 13:14 ` Integrating new MTD/jffs2 into 2.4.18 kernel Jörn Engel
2002-07-25 13:28   ` David Woodhouse
2002-07-25 15:45     ` Steven Hein
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=3D3FEE24.49D26D61@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