From: Dominic Ostrowski <dominic.ostrowski@3glab.com>
To: andy.simpkins@transcomm.uk.com, ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] FLASH file system
Date: Wed, 05 Sep 2001 01:21:00 -0000 [thread overview]
Message-ID: <3B95DEE1.646ADB50@3glab.com> (raw)
Hi Andy,
the original writer of JFFS2, David Woodhouse is now with Cygnus /
RedHat in Cambridge. His view on porting to eCos was that seperating
form vfs would be the main challenge. I'm currently having a look at
this, and I'll probably just pull out the key functionality to put into
the eCos filesystem framework.
JFFS2 source at http://www.linux-mtd.infradead.org/
David's paper on JFFS2 at http://www.infradead.org/~dwmw2/jffs2.pdf .
Dominic
next reply other threads:[~2001-09-05 1:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 1:21 Dominic Ostrowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-14 22:32 Gustav Kälvesten
2001-09-03 7:38 Simpkins, Andy
2001-09-03 2:17 Simpkins, Andy
2001-09-03 1:26 Simpkins, Andy
2001-09-03 1:34 ` Andrew Lunn
2001-05-18 0:34 [ECOS] Flash " james chen
2001-05-18 12:24 ` Jonathan Larmour
2001-06-03 19:43 ` james chen
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=3B95DEE1.646ADB50@3glab.com \
--to=dominic.ostrowski@3glab.com \
--cc=andy.simpkins@transcomm.uk.com \
--cc=ecos-discuss@sourceware.cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).