From: "John Burch" <jburch@vincisystems.com>
To: "'Jörn Engel'" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Cc: 'Jonas Holmberg' <jonas.holmberg@axis.com>
Cc: 'David Woodhouse' <dwmw2@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 10:36:14 -0400 [thread overview]
Message-ID: <000b01c31fa6$561c8e10$1200a8c0@JOHNB> (raw)
In-Reply-To: <20030521135230.GA18635@wohnheim.fh-wedel.de>
>
> On Wed, 21 May 2003 09:49:30 -0400, John Burch wrote:
> >
> > As far as I know, the feature is unique to AMD though I
> don't know if
> > it is supported across their entire product line. Also, it
> is not a
> > CFI specific feature. For example, it's discussed in the 29LV008B
> > (not a CFI compliant device) data sheet under the "Sector Erase
> > Command Sequence" section.
>
> Is there a way to know if a given chip supports this feature
> without checking the chip id against a table?
>
Not that I know of. I think the best case scenario would be that all
AMD devices supported it - then only the manuf ID would have to be
checked. However, that would have to be confirmed by AMD.
John
next prev parent reply other threads:[~2003-05-21 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2003-05-21 15:57 ` Jörn Engel
2003-05-22 12:40 ` John Burch
2003-05-22 20:31 ` jonas.holmberg
2003-05-21 9:25 Mtd block access (jffs2 formatted) and mtd char access (unformatted) on different partitions of a single flash device 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
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='000b01c31fa6$561c8e10$1200a8c0@JOHNB' \
--to=jburch@vincisystems.com \
--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