From: David Woodhouse <dwmw2@infradead.org>
To: Tom McMillan <tsm@airfiber.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Eraseblock size in jffs2 ?
Date: Wed, 10 Oct 2001 17:47:26 +0100 [thread overview]
Message-ID: <24225.1002732446@redhat.com> (raw)
In-Reply-To: <3BC47ADD.504E81C3@airfiber.com>
tsm@airfiber.com said:
> Where, exactly? Or at least, a starting point. I've just started
> looking into using JFFS2 with my DOC2000s.
Firstly, you need to deal with the restrictions imposed by NAND flash -
you can only make ten individual write() calls to any given 512-byte page
before the contents of that page become undefined until the next erase.
Because dirent nodes are quite small, it's feasible that you could try to
fit more than ten of them in a single page - basically, on the tenth write
you need to also pad to the end of the page with free space.
Secondly, you want ECC on the nodes instead of just a CRC - you want to be
able to _correct_ errors instead of just complaining about them.
That's quite a simple addition and can be implemented and tested without
even playing with real hardware. Define two new node types and make the
code deal with them accordingly. The actual ECC code is easy enough -
there's plenty of example code around, including some in nand/nand_ecc.c.
--
dwmw2
next prev parent reply other threads:[~2001-10-10 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 16:31 Eraseblock size in jffs2 ? martin.kula
2001-10-10 16:31 ` David Woodhouse
2001-10-10 16:44 ` Tom McMillan
2001-10-10 16:47 ` David Woodhouse [this message]
2001-10-10 17:16 ` martin.kula
2001-10-10 17:39 ` David Woodhouse
2001-10-10 17:58 ` martin.kula
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=24225.1002732446@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tsm@airfiber.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