From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: coywolf@lovecn.org
Cc: David Woodhouse <dwmw2@infradead.org>,
Carsten Otte <cotte@freenet.de>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
schwidefsky@de.ibm.com, akpm@osdl.org
Subject: Re: [RFC/PATCH 0/5] add execute in place support
Date: Wed, 1 Jun 2005 13:31:05 +0200 [thread overview]
Message-ID: <20050601113104.GA29116@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <2cd57c90050601023358417bbd@mail.gmail.com>
On Wed, 1 June 2005 17:33:29 +0800, Coywolf Qi Hunt wrote:
> On 5/12/05, David Woodhouse <dwmw2@infradead.org> wrote:
> > On Thu, 2005-05-12 at 10:57 +0200, Jörn Engel wrote:
> > > In principle, both the block device abstraction and the mtd
> > > abstraction fit your bill. But jffs2 doesn't, so no in-kernel fs
> > > could make use of a xip-aware mtd abstraction.
> > >
> > > Patching jffs2 for xip looks like a major effort, at best, and utterly
> > > insane at worst. I'd prefer not to go down that path.
> >
> > You and me both. The time has definitely come to recognise that JFFS2
> > needs replacing ;)
>
> I'd say yaffs seems to be a good one.
Not if you care about XIP. Yaffs won't run on NOR flashes and XIP
won't work on NAND.
Jörn
--
When you close your hand, you own nothing. When you open it up, you
own the whole world.
-- Li Mu Bai in Tiger & Dragon
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-06-01 11:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 14:29 [RFC/PATCH 0/5] add execute in place support Carsten Otte
2005-05-11 16:19 ` David Woodhouse
2005-05-11 16:35 ` Carsten Otte
2005-05-12 8:57 ` Jörn Engel
2005-05-12 9:10 ` Carsten Otte
2005-05-12 9:43 ` David Woodhouse
2005-06-01 9:33 ` Coywolf Qi Hunt
2005-06-01 11:31 ` Jörn Engel [this message]
2005-06-01 10:12 ` Coywolf Qi Hunt
2005-06-01 12:06 ` Arnd Bergmann
2005-06-01 13:39 ` Jörn Engel
2005-06-01 14:03 ` Carsten Otte
2005-06-01 14:10 ` Jörn Engel
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=20050601113104.GA29116@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=akpm@osdl.org \
--cc=cotte@freenet.de \
--cc=coywolf@lovecn.org \
--cc=dwmw2@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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;
as well as URLs for NNTP newsgroup(s).