From: arne.jonsson@i3micro.com (Arne Jonsson)
To: linux-mtd@lists.infradead.org
Subject: JFFS2 for 2.0 kernel?
Date: Mon, 24 Feb 2003 08:08:22 +0100 [thread overview]
Message-ID: <3E59C4E6.BFF740B9@i3micro.com> (raw)
In-Reply-To: 1046069750.1867.1.camel@imladris.demon.co.uk
David Woodhouse wrote:
> It would be quite a lot of work; the file system layer in Linux changed
> dramatically between the 2.0 and 2.2 kernels. You'd have a better chance
> of porting to 2.2 -- in fact I think someone's already done so.
I was afraid of that, but we need the 2.0 kernel (at least for now).
> Why do you want 2.0?
We are using using JFFS with MTD and the uClinux 2.0.38 kernel. I have
some concerns re. JFFS and powercycling and as I understand the JFFS2 is
more robust. Another option would be to make JFFS more robust but I
assume that that might be an even bigger challenge.
Best regards,
/Arne Jonsson
--
Arne Jonsson
i3 micro technology AB
Phone:+46-8-506 388 00
Fax: +46-8-506 388 75
next prev parent reply other threads:[~2003-02-24 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 6:25 JFFS2 for 2.0 kernel? Arne Jonsson
2003-02-24 6:55 ` David Woodhouse
2003-02-24 7:08 ` Arne Jonsson [this message]
2003-02-24 7:17 ` 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=3E59C4E6.BFF740B9@i3micro.com \
--to=arne.jonsson@i3micro.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