linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Laurent Lagrange" <lagrange@fr.oleane.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: RE: NAND and JFFS2 supports in Linux 2.4
Date: Thu, 13 Apr 2006 16:49:35 +0200	[thread overview]
Message-ID: <006201c65f09$7d809140$5201a8c0@GEG2400> (raw)
In-Reply-To: <1144790375.3659.3.camel@yoda.jdub.homelinux.org>


Hello

> -----Message d'origine-----
> De : Josh Boyer

> > Linux 2.4.18 or 2.4.25 do not support this device,
> Those are entire too old.
Except for some customers which must maintain kernels during many years :-)

> > Linux 2.4.31 seems supporting this device but JFFS2 is not adapted,
> NAND + JFFS2 + 2.4 is not a supported combination.
That's the problem i am facing with.

> > Linux 2.4.32 does not support this device anymore.
> Odd.  Do you have a diff from .31 to .32?
Not a diff but

1) in Linux 2.4.32, I have the following files :
Config.in        diskonchip.c  nand_bbt.c        rtc_from4.c  tx4925ndfmc.c
Makefile         edb7312.c     nand_ecc.c        s3c2410.c    tx4938ndfmc.c
Makefile.common  h1910.c       nand_ids.c        sharpsl.c*
au1550nd.c       nand.c        nandsim.c         spia.c
autcpu12.c       nand_base.c   ppchameleonevb.c  toto.c
$Id: nand_ids.c,v 1.12 2005/02/16 09:33:27 gleixner Exp $

2) in Linux 2.4.32, I just have the following files :
autcpu12.c  edb7312.c  nand.c      nand_ids.c
Config.in   Makefile   nand_ecc.c  spia.c
with a very old nand_ids.c.
$Id: nand_ids.c,v 1.1 2002/12/02 22:06:04 gleixner Exp $

> > On www.linux-mtd.infradead.org, it seems that Linux 2.4 is no more
supported.
> Well, 2.4 is supported but no new features go in that tree.  Including
> NAND support in JFFS2.  If there is a bug in the 2.4 code that is
> present in MTD/JFFS2 it can certainly still be fixed.
OK

> > Any help would be welcome
> You might try your luck with patching the latest 2.4 kernel with MTD
> CVS.  But be warned that quite a few things have changed, so
> you'd have to essentially backport.
> And keep in mind that it's not supported.
Yes, I saw  that many things have changed and are not be easily backported.
I checked the MTD CVS. All that I found are in the Linux kernel 2.4.31 or
2.6.x.

> -----Message d'origine-----
> De : Jaap-Jan Boor
> Take a look at the 2.4 http://www.denx.de kernel, it has NAND
> and jffs2 support.
Thanks but, I retreived the same files than in the other kernels.


Thanks again for your ideas
I will see what I can do

Bye
Laurent

  reply	other threads:[~2006-04-13 14:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 16:31 NAND and JFFS2 supports in Linux 2.4 Laurent Lagrange
2006-04-11 20:06 ` Jaap-Jan Boor
2006-04-11 21:19 ` Josh Boyer
2006-04-13 14:49   ` Laurent Lagrange [this message]
2006-04-13 15:03     ` Jörn Engel
2006-05-29 15:35 ` Linux kernel thread with Linux 2.6.x Laurent Lagrange
2006-05-29 17:13   ` Thiago Galesi
2006-05-30  9:46     ` Laurent Lagrange
2006-05-30 11:23       ` Jörn Engel
2006-05-30 13:17         ` almoeli
2006-05-30 22:10   ` Andy Fleming

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='006201c65f09$7d809140$5201a8c0@GEG2400' \
    --to=lagrange@fr.oleane.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).