public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Phil Thompson <phil@river-bank.demon.co.uk>,
	Henrik Nordstrom <hno@marasystems.com>,
	linux-mtd@lists.infradead.org
Subject: Re: JFFS2 Format Documentation?
Date: Tue, 28 Jan 2003 13:44:46 +0000	[thread overview]
Message-ID: <9649.1043761486@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20030128132344.GA7618@wohnheim.fh-wedel.de>

phil@river-bank.demon.co.uk said:
> David's paper is a good start but I was after a lower level of detail.
> I need  something from which I can implement a JFFS2 reader from
> scratch (ie. without  any GPL code). 

The on-medium format is very simple. The actual layout of the existing node 
types is detailed in full in include/linux/jffs2.h. In conjunction with the 
theory of operation described in the paper, these should be perfectly 
sufficient.

What exactly are you trying to achieve? Simple read-only operation or a 
fully-functional compatible file system?

--
dwmw2

  reply	other threads:[~2003-01-28 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28  9:56 JFFS2 Format Documentation? Phil Thompson
2003-01-28 11:10 ` Henrik Nordstrom
2003-01-28 12:35   ` Phil Thompson
2003-01-28 13:23     ` Jörn Engel
2003-01-28 13:44       ` David Woodhouse [this message]
2003-01-28 14:02         ` Brian J. Fox
2003-01-28 14:12           ` David Woodhouse
2003-01-28 14:11         ` Phil Thompson
2003-01-28 14:14           ` David Woodhouse
2003-01-28 16:13           ` Henrik Nordstrom
2003-01-28 16:26             ` David Woodhouse

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=9649.1043761486@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=hno@marasystems.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=phil@river-bank.demon.co.uk \
    /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