public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Charles Manning <manningc2@actrix.gen.nz>
To: David Woodhouse <dwmw2@infradead.org>,
	"Chantara Thlang" <thlang@iphase.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: need arguments to use JFFS2
Date: Sat, 7 Dec 2002 21:35:15 +1300	[thread overview]
Message-ID: <20021207083957.9465F14AC1@dragon.actrix.co.nz> (raw)
In-Reply-To: <28792.1039171331@passion.cambridge.redhat.com>

It is virtually impossible to make any firm statements without understanding 
your needs a bit better.

A few others have already covered cramfs and JFFSx. I can tell you a bit 
about YAFFS.

YAFFS only works with NAND flash. YAFFS does not provide compression (like 
JFFS does). YAFFS is faster than JFFS2 in most situations and uses less RAM.
Mileage will vary though. Compression is not necessarily a huge advantage for 
JFFSx. Some people loop-mount a cramfs image stored on YAFFS to get the 
benefits of compression as well as the faster speed for other files.

If you have NAND, then most likely YAFFS will serve you better for larger 
flash arrays (say 16MB and bigger) and JFFS2 for smaller arrays.

YAFFS will do nothing for you if you only have NOR flash.

If you're designing a new board then consider including NAND flash for 
storage (rather than NOR). NAND is cheaper, smaller (physically), bigger (in 
bytes) and faster. You can then use YAFFS or JFFS2 (even both - by 
partitioning the device).


-- Charles

      reply	other threads:[~2002-12-07  8:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 10:10 need arguments to use JFFS2 Chantara Thlang
2002-12-06 10:34 ` Wolfgang Denk
2002-12-06 10:42 ` David Woodhouse
2002-12-07  8:35   ` Charles Manning [this message]

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=20021207083957.9465F14AC1@dragon.actrix.co.nz \
    --to=manningc2@actrix.gen.nz \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=thlang@iphase.com \
    /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