From: Pantelis Antoniou <panto@intracom.gr>
To: linux-mtd@lists.infradead.org
Subject: Cram FS on NAND - How to do this?
Date: Wed, 11 Jun 2003 11:43:12 +0300 [thread overview]
Message-ID: <3EE6EBA0.3080508@intracom.gr> (raw)
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.
Looking at the code for CRAMFS I see that it would not
be very difficult to hack it to detect the bad blocks
and skip over them on startup. We could rely on
the same OOB info that JFFS2 has, and just
make a mapping list as follows:
NAND block bad? fs block
---------- ---- --------
0 n 0
1 n 1
2 y skip
3 n 2
... etc
The first complication is that CRAMFS works with
PAGE_SIZE blocks only, and that should be taken
into account.
The second is that this is the first time I hack filesystem
code and I would like to ask the list if you see any difficulties
ahead.
What are your thoughts in this?
Regards
Pantelis
next reply other threads:[~2003-06-11 8:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 8:43 Pantelis Antoniou [this message]
2003-06-11 8:51 ` Cram FS on NAND - How to do this? David Woodhouse
2003-06-11 8:58 ` Pantelis Antoniou
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=3EE6EBA0.3080508@intracom.gr \
--to=panto@intracom.gr \
--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