public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Gianluca <gianlucarenzi@eptar.com>
To: linux-mtd@lists.infradead.org
Subject: Re: jffs2 and nand mtd
Date: Thu, 11 Aug 2005 16:42:29 +0200	[thread overview]
Message-ID: <200508111642.29720.gianlucarenzi@eptar.com> (raw)
In-Reply-To: <ddf6hr$pfn$1@sea.gmane.org>

Hello,
we are working on an embedded system, but the only kernel it supports it is 
2.4.x series (microblaze based)
It has nand flash we are just wrote our drivers, but if mtd support for 2.4.x 
lacks, we cannot use them with any filesystem.

> > The best would be if you would adopt the *latest* MTD snapshot to your
> > kernel. Martin Egholm Nielsen <martin@egholm-nielsen.dk> recently ported
> > the latest MTD snapshot to a 2.4 kernel. You may ask him for a
> > patch/help.
>
> I'll help - I don't think I can create a patch that'll work directly, so
> let's see if we can get CVS HEAD up and running - step by step...
We are very glad if you "DIFFed" your harddrive mtd 2.4 sources, so it will be 
much simpler for us using them directly instead of downloading the latest 
release, then using the older macros... is it error prone doing in the 
following way?

>
> 1 )Start by fetching the source from CVS
> (http://www.linux-mtd.infradead.org/source.html)
>
> 2) Patch it in - enter the patches directory and run the patchin.sh
> script...
>
> 3) Configure the kernel for JFFS2
>
> ( 3½) If "non-standard" board, change the "proper" (vague - I know) mtd
> Makefile to include the flash-driver for your system...)
>
> 4) Try making a new kernel - this will certainly fail, since many of the
> macro's checking (and fixing) for kernel less than 2.6 has been removed...
>
> To fix the many errors in 4), you can actually compare the complaining
> files from HEAD with the ones from 2005-03-04. Many, if not all, the
> required macro's are there.
> Otherwise, I can try to see if I can create a patch/diff output stating
> the differences.
> Or, finally, you can post the errors here, or privately (not so noisy,
> but others may benefit - even if 2.4 is abandoned :-)), and we can
> fix'em together...
Anyway we will feel a lot of better if 2.4 support will NOT be abandoned at 
all, expecially for small footprint project like embedded system.

Best regards,
-- 
Gianluca Renzi
Eptar s.r.l.
Via Celletta 8/B
40026 Imola (BO) ITALY
Tel.:	+39-0542-609060
Fax.:	+39-0542-609054

  reply	other threads:[~2005-08-11 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11  7:31 jffs2 and nand mtd Alex Karev
2005-08-11  7:39 ` Artem B. Bityuckiy
2005-08-11  8:07   ` Alex Karev
2005-08-11  8:29     ` Artem B. Bityuckiy
2005-08-11  8:32       ` Artem B. Bityuckiy
2005-08-11  8:35       ` Thomas Gleixner
2005-08-11  9:58         ` Alex Karev
2005-08-11  9:42       ` Martin Egholm Nielsen
2005-08-11 14:42         ` Gianluca [this message]
2005-08-11 15:20           ` Thomas Gleixner
2005-08-11  8:33 ` 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=200508111642.29720.gianlucarenzi@eptar.com \
    --to=gianlucarenzi@eptar.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