From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: John Burch <jburch@vincisystems.com>
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 17:57:03 +0200 [thread overview]
Message-ID: <20030521155703.GA30187@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <000b01c31fa6$561c8e10$1200a8c0@JOHNB>
On Wed, 21 May 2003 10:36:14 -0400, John Burch wrote:
> >
> > 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.
Jonas Holmberg:
> Is this chip-feature "probable"? We used to do simutaneous erases in a
> bootloader, but after a while we started using chips that couldn't do
> that so we had to change the behaviour to be able to handle all sorts
> of chips. I'm not sure if CFI covers that particular feature, but it
> would be great if it did. It wouldn't be so great to have to check
> JEDEC IDs...
If I read this correctly, AMD won't confirm your assumption.
Might be another option to assume simultaneous erases work, try it,
catch the failure gracefully and turn that feature off from that point
on. Does anyone have the time and hardware to answer this question?
Jörn
--
The competent programmer is fully aware of the strictly limited size of
his own skull; therefore he approaches the programming task in full
humility, and among other things he avoids clever tricks like the plague.
-- Edsger W. Dijkstra
next prev parent reply other threads:[~2003-05-21 15:57 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
2003-05-21 15:57 ` Jörn Engel [this message]
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=20030521155703.GA30187@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=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