From: "Björn Eriksson" <bjorn@brannstrom.se>
To: <mtd@infradead.org>
Cc: <mark.langsdorf@amd.com>
Subject: Anyone using mtd on NAND flash? (Was: The archives [looking for info on AM29LV640 flash])
Date: Fri, 25 Aug 2000 13:57:11 +0200 [thread overview]
Message-ID: <000801c00e8b$9a649560$0800a8c0@win95.inteloop.se> (raw)
In-Reply-To: <0FA1031B65A9D111960900805F9FA8E103B9F079@txexmta8.amd.com>
> > I've been browsing the archive to see if anyone's used MTD on
> > AM29LV640 (64Mb, NAND I believe) parts.
>
> The spec sheet for the Am29LV640 indicates they are CFI
> parts. You should be able to use the cfi_cmdset_0002 module
> with them, though admittedly I haven't tested this myself.
I've just been across the hall to strangle our hardware engineer (who
happens to also be my boss). He /intended/ to use the AM29LV640 part but had
problems finding a reliable source for them so we're using Samsungs KM29U128
part instead.
There's no mention of CFI in the .pdf file I've got but I've detected the
KM29U128 chip using:
read_ID() /*pseudo_code*/ {
const ReadID_cmd = 0x90;
ready_chip();
chip_enable();
cmd_latch_enable();
outportb(DATA, ReadID_cmd); /*Read ID command */
cmd_latch_disable();
addr_latch_enable();
outportb(DATA, 0x00); /*1st address cycle */
addr_latch_disable();
m_code = inportb(DATA); /* Reading 2 byte data */
d_code = inportb(DATA);
return (m_code << 8) | d_code;
}
Which doesn't have much similarity to the cfi_probe.c:cfi_probe_new_chip()
function so I guess they're not CFI compliant chips; Why is that?
//Björnen.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-08-25 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-24 16:21 The archives [looking for info on AM29LV640 flash] mark.langsdorf
2000-08-25 11:57 ` Björn Eriksson [this message]
2000-08-25 12:15 ` Anyone using mtd on NAND flash? (Was: The archives [looking for info on AM29LV640 flash]) David Woodhouse
2000-09-13 3:09 ` Anyone using mtd on NAND flash? Stéphane Laroche
2000-09-13 9:13 ` 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='000801c00e8b$9a649560$0800a8c0@win95.inteloop.se' \
--to=bjorn@brannstrom.se \
--cc=mark.langsdorf@amd.com \
--cc=mdeans@algonet.se \
--cc=mtd@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