public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Cram FS on NAND - How to do this?
Date: Wed, 11 Jun 2003 11:58:42 +0300	[thread overview]
Message-ID: <3EE6EF42.7030405@intracom.gr> (raw)
In-Reply-To: <1055321465.2097.9.camel@passion.cambridge.redhat.com>

David Woodhouse wrote:

>On Wed, 2003-06-11 at 09:43, Pantelis Antoniou wrote:
>
>>Hi
>>
>>As it currently stands the only filesystems supporting
>>raw NAND flash are:
>>
>>JFFS2: Read/write, compressed, best support, slow startup.
>>YAFFS: Read/write, not compressed, newcomer, fast startup.
>>
>>I have a requirement to have a compressed read only
>>root filesystem in my board and I've come to the
>>conclussion that the best fit would be CRAMFS if only
>>had any concept of bad blocks.
>>
>
>I think it would probably be better to implement this as a block device
>driver, or perhaps as an extension to the existing mtdblock/mtdblock_ro
>drivers.
>
>
That is a valid approach.

I take it that you mean a new MTD block device over NAND that
automatically skips over bad blocks and presents an error free
block interface for use by read only filesystems.

Thanks, it really pays off to ask questions first, and hack afterwards ;)

Regards

Pantelis

  reply	other threads:[~2003-06-11  8:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11  8:43 Cram FS on NAND - How to do this? Pantelis Antoniou
2003-06-11  8:51 ` David Woodhouse
2003-06-11  8:58   ` Pantelis Antoniou [this message]
2003-06-11  9:04     ` David Woodhouse
2003-06-11  9:10       ` Russ Dill
2003-06-11  9:12         ` David Woodhouse
2003-06-11  9:01 ` Jasmine Strong
2003-06-11  9:54   ` Pantelis Antoniou
2003-06-11 10:24     ` angainor
2003-06-11 19:22     ` Russ Dill
2003-06-12  8:22       ` Pantelis Antoniou
2003-06-12  9:06 ` Thomas Gleixner
2003-06-12  8:15   ` Pantelis Antoniou
2003-06-12 23:13 ` Charles Manning
2003-06-13 12:18   ` Jasmine Strong
2003-06-13 16:30     ` Brian J. Fox
2003-06-13 16:33       ` Jasmine Strong
2003-06-13 16:45         ` Brian J. Fox

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=3EE6EF42.7030405@intracom.gr \
    --to=panto@intracom.gr \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.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