From: David Woodhouse <dwmw2@infradead.org>
To: Mike Voytovich <mvoytovich@coactive.com>
Cc: Steve Kranz <skranz@ridgerun.com>, linux-mtd@lists.infradead.org
Subject: Re: MTD/mtdblock.c uclinux 2.0.38?
Date: Wed, 18 Jul 2001 07:16:39 +0100 [thread overview]
Message-ID: <18526.995436999@redhat.com> (raw)
In-Reply-To: <7118259C3044D311942700508B2CA5BB7412DE@balance.coactive.com>
mvoytovich@coactive.com said:
> One big issue is that JFFS2 seems to rely on the dirent cache, which
> isn't present in the 2.0.x kernel. So, I suppose that would have to
> be backported from 2.2.x (if that's even a reasonable task).
Wouldn't it be easier to forward-port uCLinux to 2.4? Didn't someone
already do that, in fact?
> I don't know what other kernel dependencies (besides dirent cache)
> there are for JFFS2... I wonder if anyone has been successful in
> getting JFFS2 working with 2.0.x?? Any feedback would be
> appreciated...
JFFS1 will be easier. JFFS2 is possible but may be a lot of work. The dcache
thing should be the biggest problem - and that's possible to work around. I
wouldn't backport the whole of the dcache thing to 2.0 - that would involve
completely rewriting the VFS. Just provide internally to the JFFS2 code
sufficient dcache stuff for it to work. Pretend dentries are JFFS2-internal
data structures.
--
dwmw2
next prev parent reply other threads:[~2001-07-18 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 23:02 MTD/mtdblock.c uclinux 2.0.38? Mike Voytovich
2001-07-18 6:16 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-18 6:50 Mike Voytovich
2001-07-16 23:00 Mike Voytovich
2001-07-17 7:06 ` David Woodhouse
2001-07-09 13:42 Steve Kranz
2001-07-11 9:11 ` David Woodhouse
2001-07-11 19:30 ` Steve Kranz
2001-07-11 20:36 ` Herman Oosthuysen
2001-07-11 22:28 ` 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=18526.995436999@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mvoytovich@coactive.com \
--cc=skranz@ridgerun.com \
/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