From: Chris AtLee <catlee@canada.com>
To: Linux MTD <linux-mtd@lists.infradead.org>
Subject: JFFS & MTDBLOCK
Date: 18 Jun 2002 11:29:27 -0400 [thread overview]
Message-ID: <1024414167.9366.9.camel@geb> (raw)
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
Hi,
Just re-reading the mtd-jffs HOWTO to see if I can glean any additional
information from it and I noticed the paragraphs that read,
"You must use (for all practical purposes that involve writing) JFFS on
raw flash MTD devices. This is because JFFS provides a robust writing
and wear leveling mechanism. See FAQ for more info.
If you only want the file-system to be writable while you're developing,
but will ship the units read-only, it's acceptable to use the MTDBLOCK
device, which performs writes by reading the entire erase block, erasing
it, changing the range of bytes which were written to, and writes it
back to the flash. Obviously that's not something you want happening in
production, but for development it's OK."
I'm not sure that I understand what this means...
Does it mean that for production units where you want the filesystem to
be writeable you should use JFFS on a non-MTDBLOCK device?
Or does it mean that using a filesystem other than JFFS for writing to a
MTDBLOCK device is probably a bad idea?
Thanks,
Chris
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-06-18 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 15:29 Chris AtLee [this message]
2002-06-18 15:37 ` JFFS & MTDBLOCK David Woodhouse
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=1024414167.9366.9.camel@geb \
--to=catlee@canada.com \
--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