public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Terence Soh <gopher@singnet.com.sg>
To: Russ Dill <russ.dill@gmail.com>, Josh Boyer <jwboyer@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Cramfs on NAND
Date: Mon, 13 Mar 2006 08:34:10 +0800	[thread overview]
Message-ID: <4414BE02.3080300@singnet.com.sg> (raw)
In-Reply-To: <f9d2a5e10603100936s43f3d7bdoe8d118b9009ff925@mail.gmail.com>

Hi,

>>Yes, it's still true.  CRAMFS expects it's data to be contiguous so
>>unless you have something similar to a flash translation layer that
>>hides the bad blocks, insanity will ensue.
FTL will not work for me because of the licensing issues :(.

>>Could you use a read-only JFFS2 partition?
Besides the read-only characteristic, I'm also looking at fast mount 
time. I guess I should take a look at YAFFS.

Question: Does a read-only JFFS2/YAFFS partition means that there will 
not be any wear-levelling performed?

> 
> 
> The other solution is to use an ftl ontop of the flash, and then put a
> cramfs on that. Of course, that depends on you living somewhere where
> algorithms are not restricted to those with the license to use them.
> (iirc)
> 

Bye and thanks for your time,
Terence.

  reply	other threads:[~2006-03-13  1:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1FErAE-00004u-2M@canuck.infradead.org>
2006-03-03  1:37 ` Cramfs on NAND Terence Soh
2006-03-10 13:06   ` Josh Boyer
2006-03-10 17:36     ` Russ Dill
2006-03-13  0:34       ` Terence Soh [this message]
2006-03-18  2:43       ` Sean Kelley

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=4414BE02.3080300@singnet.com.sg \
    --to=gopher@singnet.com.sg \
    --cc=jwboyer@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=russ.dill@gmail.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