From: "John Burch" <jburch@vincisystems.com>
To: <linux-mtd@lists.infradead.org>
Subject: Mtd block access (jffs2 formatted) and mtd char access (unformatted) on different partitions of a single flash device
Date: Tue, 20 May 2003 16:53:30 -0400 [thread overview]
Message-ID: <002701c31f11$e009ce70$1200a8c0@JOHNB> (raw)
Is there a preferred way to access different mtd partitions of a single
flash device when certain accesses will be (1) block oriented via
standard file I/O of a jffs2 file system mounted on a /dev/mtdblockN
device and other accesses will be (2) character oriented via 'dd' (or
some other mechanism?) of unformatted/raw flash using /dev/mtdN? Are
there any possibly bad interactions between mtd char and block device
access to the same device?
I've adopted a system that uses a driver with its own flash support to
read/write raw (non-jffs2) portions of the flash, while application code
uses standard file I/O to read/write jffs2 partitions on the same
device. I'm concerned that these accesses may clash and possibly result
in corrupted flash, crashed kernel, etc. Is this a legitimate concern
or does the mtd driver check flash status prior to any operations?
Thanks,
John
next reply other threads:[~2003-05-20 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 20:53 John Burch [this message]
2003-05-20 21:13 ` Mtd block access (jffs2 formatted) and mtd char access (unformatted) on different partitions of a single flash device Charles Manning
2003-05-21 9:05 ` Jörn Engel
2003-05-21 9:25 ` David Woodhouse
2003-05-21 12:33 ` Mtd block access (jffs2 formatted) and mtd char access(unformatted) on different partitions of a single flashdevice John Burch
2003-05-21 12:35 ` Mtd block access (jffs2 formatted) and mtd char access(unformatted) on different partitions of a single flash device 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='002701c31f11$e009ce70$1200a8c0@JOHNB' \
--to=jburch@vincisystems.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