This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Simple flash filesystem?
- To: Kristian Otnes <kristian dot otnes at tevero dot no>
- Subject: [ECOS] Re: Simple flash filesystem?
- From: "Grant Edwards" <grante at visi dot com>
- Date: Tue, 06 Feb 2001 20:50:30 GMT
- Cc: ecos-discuss at sources dot redhat dot com
- References: <981465384.28425.ezmlm@sources.redhat.com> <3A805EF4.3D21C830@tevero.no>
Kristian Otnes writes:
[excellent analsys of problem]
> Alas, it is hard to find any free and good system on the
> net... I couldn't when I needed it. The Journalling flash file system
> (http://www.developer.axis.com/software/jffs/) is possibly one
> candidate, but it is for Linux (maybe portable). I don't know
> the situation of its overall performance and recovery mechanisms...
I found jffs and a couple other journalling approaches to implimenting
a block device underneath a Unix or DOS filesystem, but they all seemed
way too big/complex when my filesystem isn't going to be more than a few
hundred KBytes and will be rarely written to. For now, I'm going to try
to use a ROM filesystem and have users download the whole directory
tree when a file changes.
It could be worse, I could ask them to link the files as data with the
application code and eCos.
Maybe in phase II (AKA: the list of things that will never get done)
I'll come up with a simple flash filesystem for my situation: writes
are rare and are allowed to block reads for a long time (several seconds).
--
Grant Edwards
grante@visi.com