From: Geoffrey Espin <espin@idiom.com>
To: linux-mtd@lists.infradead.org
Subject: 4 x AMD29LV800B CFI?
Date: Fri, 23 Nov 2001 13:01:36 -0800 [thread overview]
Message-ID: <20011123130136.A94932@idiom.com> (raw)
In-Reply-To: <E1669aI-0001iv-00@pentafluge.infradead.org>; from linux-mtd-request@lists.infradead.org on Tue, Nov 20, 2001 at 12:01:02PM +0000
Is there a definitive URL to discover what chips are CFI and
which are not? I've Googled the planet for the AMD29LV800B family.
The chip is appears in mtd/chips/amd_flash.c, not necessarily
CFI. I found a nearly dead link on AMD site to source code:
http://www.amd.com/us-en/assets/content_type/utilities/cfiflash.h.txt
http://www.amd.com/us-en/assets/content_type/utilities/cfiflash.c.txt
which contains the part, yet the datasheet:
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/21531.pdf
doesn't list it as having CFI.
The NEC/MIPS "Korva" board I'm trying to get this working on has
4 x AMD29LV800B's byte interleaved for 4MB total. I've tinkered
with cfi/jedec/amd_flash and not one of them will recognize the
part(s). After sending the command code(s), it replies with the
contents at the particular offset, not the chip code. Perhaps
my h/w setup is insisting that all 4 parts are programmed at
once? I see ifdef SOMEONE_ACTUALLY... for width 4 type 32
interleave 4; maybe this means generate the right pattern? I'm
now driven to more furious surgery, it seems. :-(
Geoff
--
Geoffrey Espin
espin@idiom.com
next parent reply other threads:[~2001-11-23 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1669aI-0001iv-00@pentafluge.infradead.org>
2001-11-23 21:01 ` Geoffrey Espin [this message]
2001-11-27 11:05 ` 4 x AMD29LV800B CFI? David Woodhouse
2001-11-28 3:30 ` Geoffrey Espin
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=20011123130136.A94932@idiom.com \
--to=espin@idiom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.