From: Angus CLARK <angus.clark@st.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH (mtd-www) 05/13] nand-data: remove incorrect/duplicate Numonyx NAND01G devices
Date: Fri, 09 Dec 2011 11:04:00 +0000 [thread overview]
Message-ID: <4EE1EB20.4070001@st.com> (raw)
In-Reply-To: <CAN8TOE-+7OVNiexKkP1yXYm6z5wx7dyOh0FhCkLzov8M=suVDQ@mail.gmail.com>
Hi Brian,
On 12/07/2011 07:28 PM, Brian Norris wrote:
> On Tue, Dec 6, 2011 at 4:07 AM, Angus CLARK <angus.clark@st.com> wrote:
>> The table includes two entries for each of the following Numonyx devices:
>> NAND01GR3B2B, NAND01GW3B2B, NAND01GR4B2B, NAND01GW4B2B. This patch removes the
>> second set since it disagrees with the datasheets I have with regards to ONFI
>> V1.0 support and the READID data.
>
> This one's strange. I have 2 different data sheets for this part (both
> Numonyx) and I have a sample NAND that's labeled "ST Micro
> NAND01GW3B2C." The sample has ID 0x20F1001D, matching the row for
> NAND01GW3B2B which you are deleting. The chip *is* ONFI-capable, and
> yields a manufacturer/part string of "ST Micro NAND01GW3B2CN6."
>
Yes, the "Rev C" version, NAND01GW3B2C, does support ONFI, and returns a READID
of 0x20F1001D. (Although interestingly, on my sample, it returns the "ONFI"
signature but not the parameter page - I will investigate further!).
I do not have an equivalent "Rev B" sample (ie NAND01GW3B2B), but all the
information I have suggests the "Rev B" family of devices does not support ONFI,
and the READID matches the "first" set of entries in the datasheet.
Perhaps this is a "Rev C" vs "Rev B" issue, in which case, I would suggest
applying the patch and maybe adding the "Rev C" versions to the table. What do
you think?
Cheers,
Angus
> So I'm not sure what to say. These data sheets are old enough I can't
> find a public, updated version of the data sheet - only
> company-internal copies of varying age - and everything is complicated
> because ST Micro was bought by Numonyx, who rebranded some chips.
>
> Unless you have a better suggestion, I might add a note instead of
> deleting. Something like:
>
> "ST/Numonyx chips may come with varying ID, ONFI capability"
>
> Brian
>
--
-------------------------------------
Angus Clark
ST Microelectronics (R&D) Ltd.
1000 Aztec West, Bristol, BS32 4SQ
email: angus.clark@st.com
tel: +44 (0) 1454 462389
st-tina: 065 2389
-------------------------------------
next prev parent reply other threads:[~2011-12-09 11:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 12:07 [PATCH (mtd-www) 01/13] nand-data: update TC58DVM72A1TG00 BBM info Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 02/13] nand-data: updates to S30ML-P devices Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 03/13] nand-data: Samsung devices: fix ID Length = "5?" Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 04/13] nand-data: Fix Numonyx 'NAND02GW42C' name Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 05/13] nand-data: remove incorrect/duplicate Numonyx NAND01G devices Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 06/13] nand-data: fix name for Samsung "K9XDG08U5D" Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 07/13] nand-data: fix data for Numonyx NAND08GW3F2B device Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 08/13] nand-data: fix ID Length for Hynix "HY27US{08, 16}12(1/2)B" devices Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 09/13] nand-data: Update BBM info for Toshiba TC58DVG02A5 Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 10/13] nand-data: update READID data for family of Micron devices Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 11/13] nand-data: update MT29F8G08AB--- device IDs Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 12/13] nand-data: add columns to the table Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 13/13] nand-data: add devices Angus CLARK
2011-12-07 20:03 ` [PATCH (mtd-www) 09/13] nand-data: Update BBM info for Toshiba TC58DVG02A5 Brian Norris
2011-12-07 19:52 ` [PATCH (mtd-www) 08/13] nand-data: fix ID Length for Hynix "HY27US{08, 16}12(1/2)B" devices Brian Norris
2011-12-09 11:45 ` Angus CLARK
2011-12-07 19:43 ` [PATCH (mtd-www) 07/13] nand-data: fix data for Numonyx NAND08GW3F2B device Brian Norris
2011-12-07 19:38 ` [PATCH (mtd-www) 06/13] nand-data: fix name for Samsung "K9XDG08U5D" Brian Norris
2011-12-09 11:38 ` Angus CLARK
2011-12-09 20:49 ` Brian Norris
2011-12-07 19:28 ` [PATCH (mtd-www) 05/13] nand-data: remove incorrect/duplicate Numonyx NAND01G devices Brian Norris
2011-12-09 11:04 ` Angus CLARK [this message]
2011-12-09 21:14 ` Brian Norris
2011-12-13 14:24 ` Angus CLARK
2011-12-07 18:58 ` [PATCH (mtd-www) 04/13] nand-data: Fix Numonyx 'NAND02GW42C' name Brian Norris
2011-12-07 18:55 ` [PATCH (mtd-www) 03/13] nand-data: Samsung devices: fix ID Length = "5?" Brian Norris
2011-12-07 18:49 ` [PATCH (mtd-www) 02/13] nand-data: updates to S30ML-P devices Brian Norris
2011-12-09 8:35 ` Angus CLARK
2011-12-09 20:42 ` Brian Norris
2011-12-06 21:02 ` [PATCH (mtd-www) 01/13] nand-data: update TC58DVM72A1TG00 BBM info Artem Bityutskiy
2011-12-07 18:14 ` Brian Norris
2011-12-08 22:16 ` Artem Bityutskiy
2011-12-08 22:18 ` Artem Bityutskiy
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=4EE1EB20.4070001@st.com \
--to=angus.clark@st.com \
--cc=computersforpeace@gmail.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;
as well as URLs for NNTP newsgroup(s).