From: Eduardo Sabaj <esabaj@hasar.com>
To: linux-mtd@lists.infradead.org
Subject: [Fwd: Re: [ECOS] JFFS2]
Date: Fri, 02 Jan 2004 14:59:41 -0300 [thread overview]
Message-ID: <3FF5B18D.EC80AA1D@hasar.com> (raw)
Dear sir,
I would be grateful if you could answer some of questions that are
indicated below ...
On top of that, could you please tell me what other file systems (and on
which media - flash, disk, etc) are supported by eCos?
Thanks for all,
Eduardo
-------- Original Message --------
Subject: Re: [ECOS] JFFS2
Date: 02 Jan 2004 09:17:31 -0700
From: Gary Thomas <gary@mlbassoc.com>
Organization: MLB Associates
To: Eduardo Sabaj <esabaj@hasar.com>
CC: ecos-discuss@sources.redhat.com
References: <3FF59306.6704AE5B@hasar.com>
On Fri, 2004-01-02 at 08:49, Eduardo Sabaj wrote:
> I am interested in building an embedded application using the eCos, but
> I have some questions about it.. I read that one of the file systems
> that is supported is JFFS2 but the question is, if it is a file system
> that runs only over a flash device (can I have a JFFS2 file system on
> DiskOnModule?)
> On the other hand, I wonder if JFFS2 is well protected over power fails
> (I mean if the file system avoid losing information after the power
> fail) ?
This question would probably be better answered by the folks that
support JFFS2 - try linux-mtd@lists.infradead.org
JFFS2 should work with most any type of FLASH device, but AFAIK there
are no drivers currently available for DiskOnModule for eCos (but you
should be able to write them). As for persistence, JFFS2 stands for
"Journaling Flash File System v2", which means that data is kept in
a journaled fashion and should be safe to recover, even after a
power failure.
Again, discuss this with the MTD/JFFS2 folks for the best advice.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
reply other threads:[~2004-01-02 18:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FF5B18D.EC80AA1D@hasar.com \
--to=esabaj@hasar.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