From: David Woodhouse <dwmw2@infradead.org>
To: Chris AtLee <catlee@canada.com>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: JFFS & MTDBLOCK
Date: Tue, 18 Jun 2002 16:37:36 +0100 [thread overview]
Message-ID: <14188.1024414656@redhat.com> (raw)
In-Reply-To: <1024414167.9366.9.camel@geb>
catlee@canada.com said:
> 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?
It means the latter. When you mount JFFS/JFFS2 on an mtdblock device, it
doesn't actually _use_ the read/modify/erase/writeback algorithm described
-- or indeed use the mtdblock driver at all -- it just uses the minor
number of the mtdblock device you specified to get a handle on the real
underlying MTD device.
Using any _other_ file system than JFFS/JFFS2 on the mtdblock device other
than in read-only mode is a bad idea.
--
dwmw2
prev parent reply other threads:[~2002-06-18 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 15:29 JFFS & MTDBLOCK Chris AtLee
2002-06-18 15:37 ` David Woodhouse [this message]
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=14188.1024414656@redhat.com \
--to=dwmw2@infradead.org \
--cc=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