public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "John Burch" <jburch@vincisystems.com>
To: "'David Woodhouse'" <dwmw2@infradead.org>,
	"'Jörn Engel'" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Subject: RE: Mtd block access (jffs2 formatted) and mtd char access(unformatted) on different partitions of a single flashdevice
Date: Wed, 21 May 2003 08:33:44 -0400	[thread overview]
Message-ID: <000701c31f95$38ad1040$1200a8c0@JOHNB> (raw)
In-Reply-To: <1053509146.20074.2584.camel@passion.cambridge.redhat.com>

> > 
> > What does "driver" mean? If you have two in-kernel drivers for the 
> > same flash chip, they will use different locks and things 
> will break. 
> > If that is a user-space driver, using the /dev/mtdX 
> devices, you are 
> > perfectly safe. Which one is it?
> 
> Hmmm. What he actually said was 'driver with its own flash 
> support', which sounds bad. As long as everything accessing 
> the flash goes through the MTD driver for the flash, using 
> its read/write/erase functions rather than banging on the 

When accessing "raw" flash via the char driver, how can I initiate a
sector erase?  Also, does the mtd driver for AMD CFI devices handle
AMD's ability to support erasure of multiple sectors simultaneously?

> hardware directly, it'll be fine. If your raw driver is 
> actually dealing with the flash driver directly, that's broken.
> 

David has it right.  The raw "in-kernel" driver deals with flash
directly on its own, not through mtd.

  reply	other threads:[~2003-05-21 12:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 20:53 Mtd block access (jffs2 formatted) and mtd char access (unformatted) on different partitions of a single flash device John Burch
2003-05-20 21:13 ` Charles Manning
2003-05-21  9:05 ` Jörn Engel
2003-05-21  9:25   ` David Woodhouse
2003-05-21 12:33     ` John Burch [this message]
2003-05-21 12:35       ` Mtd block access (jffs2 formatted) and mtd char access(unformatted) " David Woodhouse
     [not found] <3C6BEE8B5E1BAC42905A93F13004E8AB01CAF732@mailse01.axis.se>
2003-05-21 13:49 ` Mtd block access (jffs2 formatted) and mtd char access(unformatted) on different partitions of a single flashdevice John Burch
2003-05-21 13:52   ` Jörn Engel
2003-05-21 14:36     ` John Burch
2003-05-21 15:57       ` Jörn Engel
2003-05-22 12:40         ` John Burch
2003-05-22 20:31   ` jonas.holmberg

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='000701c31f95$38ad1040$1200a8c0@JOHNB' \
    --to=jburch@vincisystems.com \
    --cc=dwmw2@infradead.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --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