From: York Sun <yorksun@freescale.com>
To: linux-mtd@lists.infradead.org
Subject: DQ7 vs DQ6 in flash erase/write
Date: Wed, 20 Oct 2004 09:19:08 -0500 [thread overview]
Message-ID: <1098281947.14086.8.camel@localhost.localdomain> (raw)
In-Reply-To:
Shawn,
I have the same problem you had for AMD flash. Polling DQ6 doesn't
always work while polling DQ7 does. I have two board, one is with
AM29LV641D, the other is with AM29LV641M. The latter one always work for
both polling.
Did you figure it out?
--
Best regards,
York Sun, Ph.D
Metrowerks
Freescale Semiconductor Inc.
Phone: (512) 996-5252
Email: yorksun@freescale.com
This email, and any associated attachments have been classified as:
[x] Freescale Semiconductor General Business
[ ] Freescale Semiconductor Internal Use Only
[ ] Freescale Semiconductor Confidential Proprietary
next reply other threads:[~2004-10-20 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 14:19 York Sun [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-12 20:52 DQ7 vs DQ6 in flash erase/write Shawn Jin
2004-03-15 10:32 ` David Vrabel
2004-03-15 20:14 ` Shawn Jin
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=1098281947.14086.8.camel@localhost.localdomain \
--to=yorksun@freescale.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