JFFS - ready for submission into 2.[34]? (fwd)

Bjorn Wesen bjorn.wesen at axis.com
Fri Jun 9 08:51:02 EDT 2000

In case you did not get this - there was some mail problems between axis
and infradead.org.

---------- Forwarded message ----------
Date: Fri, 9 Jun 2000 14:24:54 +0200 (CEST)
From: Bjorn Wesen <bjornw at axis.com>
To: Jason Gunthorpe <jgg at deltatee.com>
Cc: mtd at infradead.org, jffs-dev at axis.com
Subject: Re: JFFS - ready for submission into 2.[34]? 

On Thu, 8 Jun 2000, Jason Gunthorpe wrote:
> > mkfs.jffs and in the filesystem itself of course. But the on-flash
> > node-structure of JFFS is so simple that mkfs.jffs is simple enough to
> > warrant it I think.
> Is the on flash structure documented? I need to write a simple read-only
> driver for bootloaders. (see the boot stuff in MTD CVS, if it is still the
> things I cooked up..)

It's "documented" in the .h file describing the struct, of course :)

In essence if you're just going to read say a file, the simplest is to
write a small function that scans the entire flash looking for the most
up-to-date version of a specified node. Then you do that scan for each
path component of the file you need. Once for /, then for bin, then for
myboot (for example).

Just remember that you do need to scan the entire flash because nodes that
get replaced are still there, so you need to find the one with the highest
version count (or whatever it is).

If you write that simple file-finder, do post it back here, it would be
a useful example tool. 


To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org

More information about the linux-mtd mailing list