From: David Woodhouse <dwmw2@infradead.org>
To: Daniel Egger <de@axiros.com>
Cc: cijoml@volny.cz, linux-kernel@vger.kernel.org
Subject: Re: jff2 filesystem in vanilla
Date: Sat, 05 Jun 2004 00:09:50 +0100 [thread overview]
Message-ID: <1086390590.4588.70.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <F84CE3DA-B605-11D8-B781-000A958E35DC@axiros.com>
On Fri, 2004-06-04 at 11:02 +0200, Daniel Egger wrote:
> JFFS2 is included in the standard kernels IIRC, however I'd recommend
> using the CVS version from the official repository as there are huge
> improvements in there.
JFFS2 in the 2.4 kernel is an old stable branch.
The code in 2.6 and in CVS is much faster to mount, especially, and it
also supports NAND flash.
Linus' tree is updated periodically when I'm sufficiently happy with the
stability of the development tree in CVS, and when I have time to merge
it, test it and read through all the changes for sanity -- which often
involves redoing some of them. You should be OK using what's in the
kernel -- let me know if you have problems.
> To use it on a non-MTD[1] device you will need an emulation layer,
> the pseudo Block-MTD device. And you will need some additional partition
> using ext2/ext3/reiserfs/FAT containing the kernel for your Grub/LILO
> bootloader.
JFFS2 on blkmtd isn't ideal -- it's designed to work on real flash. But
it works. It could do with someone making it use the stuff we did for
NAND -- batching writes into 512-byte chunks etc.
--
dwmw2
next prev parent reply other threads:[~2004-06-04 23:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 8:00 Michal Semler
2004-06-04 9:02 ` Daniel Egger
2004-06-04 23:09 ` David Woodhouse [this message]
2004-06-05 8:27 ` Daniel Egger
2004-06-05 8:46 ` David Woodhouse
2004-06-05 13:38 ` Daniel Egger
2004-06-05 17:01 ` David Woodhouse
2004-06-07 16:19 ` Jörn Engel
2004-06-08 9:31 ` P
2004-06-13 8:39 ` Daniel Egger
2004-06-13 21:33 ` Bernd Eckenfels
2004-06-14 11:45 ` Jörn Engel
2004-06-14 12:03 ` Daniel Egger
2004-06-15 0:12 ` Thomas Gleixner
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=1086390590.4588.70.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=cijoml@volny.cz \
--cc=de@axiros.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®