From: Wolfram Sang <w.sang@pengutronix.de>
To: yidong zhang <zhangyd6@gmail.com>
Cc: linux-mtd@lists.infradead.org,
Guillaume LECERF <glecerf@gmail.com>,
taliaferro62@gmail.com, David.Woodhouse@intel.com,
yegorslists@googlemail.com
Subject: Re: Re :Re: [Help] SST39VF6401B Support
Date: Sat, 16 Oct 2010 15:17:52 +0200 [thread overview]
Message-ID: <20101016131752.GA2676@pengutronix.de> (raw)
In-Reply-To: <AANLkTikOKx7hhF9jffRF+HvfwYFDghZAzNBgO-pZpAFv@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Sat, Oct 16, 2010 at 08:25:44PM +0800, yidong zhang wrote:
> Hi
> Thanks for your reply. In the cfi_nopri_fixup_table, i added the
> below code as you did.
> { CFI_MFR_SST, 0x236D, fixup_sst39vf_rev_b, NULL, }, // SST39VF6401B
OK, please just use C-style comments (I just sent another patch
converting the others). Also, would be nice if you could check the
datasheet for other IDs mentioned there and add them, too.
> And the flash can get detected. But i still have one confusion.
> According to the data sheets Table 6, in the 6th bus write cycle.
> 39VF6401B uses 0x50 and 39VF6401 uses 0x30. If 39VF6401B uses 0x30 in
Ouch! Is this true for the other 39VF*-non-B and B-versions, too?
Adding Guillaume to CC...
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-10-16 13:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 7:08 Re :Re: [Help] SST39VF6401B Support yidong zhang
2010-10-16 10:07 ` Wolfram Sang
2010-10-16 12:25 ` yidong zhang
2010-10-16 13:17 ` Wolfram Sang [this message]
2010-10-16 14:20 ` yidong zhang
2010-10-18 4:00 ` yidong zhang
2010-10-18 11:41 ` Wolfram Sang
2010-10-18 13:05 ` yidong zhang
2010-10-18 13:41 ` Guillaume LECERF
2010-10-21 10:33 ` Guillaume LECERF
[not found] ` <AANLkTinLTW25faUTBfKBVcpFXFrtv1UhWWDN9Dgm1jOH@mail.gmail.com>
[not found] ` <AANLkTiknoWR_v-TfV5M5ZwsV3Lsk=EDDD185kXp4B96V@mail.gmail.com>
[not found] ` <AANLkTin-4fGYzD8a9rDp9M7YEk1y7JbXmZVLjA=3iU3Q@mail.gmail.com>
2010-10-21 15:24 ` Guillaume LECERF
2010-10-22 0:17 ` yidong zhang
2010-10-22 7:52 ` Guillaume LECERF
2010-10-22 8:46 ` yidong zhang
2010-10-22 10:41 ` Guillaume LECERF
2010-10-22 15:07 ` yidong zhang
2010-10-22 15:36 ` Guillaume LECERF
2010-10-22 15:42 ` yidong zhang
2010-10-22 17:50 ` Fabio Giovagnini
2011-06-16 0:55 ` Flávio Silveira
2011-06-20 3:12 ` Flávio Silveira
2011-06-20 3:36 ` yidong zhang
2011-06-20 23:55 ` Flávio Silveira
2011-12-08 21:21 ` Flávio Silveira
2011-12-09 23:15 ` Flávio Silveira
2011-12-10 0:54 ` Guillaume LECERF
2011-12-10 1:56 ` Flávio Silveira
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=20101016131752.GA2676@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=David.Woodhouse@intel.com \
--cc=glecerf@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=taliaferro62@gmail.com \
--cc=yegorslists@googlemail.com \
--cc=zhangyd6@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).