[PATCH (mtd-www) 2/7] nand-data: rename duplicate Numonyx NAND01G devices as 'Rev C'

public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed

From: Angus CLARK <angus.clark@st.com>
To: linux-mtd@lists.infradead.org
Cc: Angus Clark <angus.clark@st.com>
Subject: [PATCH (mtd-www) 2/7] nand-data: rename duplicate Numonyx NAND01G devices as 'Rev C'
Date: Thu,  5 Jan 2012 16:13:55 +0000	[thread overview]
Message-ID: <1325780040-19809-2-git-send-email-angus.clark@st.com> (raw)
In-Reply-To: <1325780040-19809-1-git-send-email-angus.clark@st.com>

The table includes two entries for each of the following Numonyx devices:
NAND01GR3B2B, NAND01GW3B2B, NAND01GR4B2B, NAND01GW4B2B.  After further analysis,
it seems that the data for the second set of entries actaully coresponds to the
'Rev C' version of the devices, rather than 'Rev B' as suggested by the names.
This patch renames the second set of entries with the 'Rev C' names.

Signed-off-by: Angus Clark <angus.clark@st.com>
---
 nand-data/nanddata.csv |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/nand-data/nanddata.csv b/nand-data/nanddata.csv
index 6929691..5bde226 100644
--- a/nand-data/nanddata.csv
+++ b/nand-data/nanddata.csv
@@ -121,10 +121,10 @@
 "Numonyx","NAND02GW3B2C","0x20","0xDA","0x20DA801D",256,2048,64,"128 KB","x8","N/A","1st page (1st or 6th byte in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,TRUE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
 "Numonyx","NAND02GR4B2C","0x20","0xBA","0x20BA8055",256,2048,64,"128 KB","x16","N/A","1st page (1st word in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,FALSE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
 "Numonyx","NAND02GW4B2C","0x20","0xCA","0x20CA805D",256,2048,64,"128 KB","x16","N/A","1st page (1st word in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,FALSE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
-"Numonyx","NAND01GR3B2B","0x20","0xA1","0x20A10015",128,2048,64,"128 KB","x8",1.0,"1st page (1st or 6th byte in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,TRUE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
-"Numonyx","NAND01GW3B2B","0x20","0xF1","0x20F1001D",128,2048,64,"128 KB","x8",1.0,"1st page (1st or 6th byte in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,TRUE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
-"Numonyx","NAND01GR4B2B","0x20","0xB1","0x20B10055",128,2048,64,"128 KB","x16",1.0,"1st page (1st word in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,FALSE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
-"Numonyx","NAND01GW4B2B","0x20","0xC1","0x20C1005D",128,2048,64,"128 KB","x16",1.0,"1st page (1st word in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,FALSE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
+"Numonyx","NAND01GR3B2C","0x20","0xA1","0x20A10015",128,2048,64,"128 KB","x8",1.0,"1st page (1st or 6th byte in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,TRUE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
+"Numonyx","NAND01GW3B2C","0x20","0xF1","0x20F1001D",128,2048,64,"128 KB","x8",1.0,"1st page (1st or 6th byte in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,TRUE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
+"Numonyx","NAND01GR4B2C","0x20","0xB1","0x20B10055",128,2048,64,"128 KB","x16",1.0,"1st page (1st word in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,FALSE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
+"Numonyx","NAND01GW4B2C","0x20","0xC1","0x20C1005D",128,2048,64,"128 KB","x16",1.0,"1st page (1st word in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,FALSE,"22-bit/2048-bits",1,4,"Extended ID decode",TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
 "Hynix","HY27UF082G2A","0xAD","0xDA","0xADDA801D00",256,2048,64,"128 KB","x8","N/A","1st or 2nd page (1st byte in OOB = non FFh)",TRUE,FALSE,FALSE,TRUE,FALSE,"1-bit/528-byte",1,5,"Extended ID decode",TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
 "Hynix","HY27UF162G2A","0xAD","0xCA","0xADCA805D00",256,2048,64,"128 KB","x16","N/A","1st or 2nd page (1st word in OOB = non FFh)",TRUE,FALSE,FALSE,TRUE,FALSE,"1-bit/528-byte",1,5,"Extended ID decode",TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
 "Samsung","K9G8G08B0A","0xEC","0xD3","0xECD314A564",1024,2048,64,"256 KB","x8","N/A","Last page (1st byte in OOB = non FFh)",FALSE,TRUE,FALSE,TRUE,FALSE,"4-bit/512-byte",2,5,"Extended ID decode",TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,
-- 
1.5.3.3

next prev parent reply	other threads:[~2012-01-05 16:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 16:13 [PATCH (mtd-www) 1/7] nand-data: updates to S30ML-P devices Angus CLARK
2012-01-05 16:13 ` Angus CLARK [this message]
2012-01-07  3:14   ` [PATCH (mtd-www) 2/7] nand-data: rename duplicate Numonyx NAND01G devices as 'Rev C' Brian Norris
2012-01-05 16:13 ` [PATCH (mtd-www) 3/7] nand-data: update READID data for family of Micron devices Angus CLARK
2012-01-07  3:21   ` Brian Norris
2012-01-05 16:13 ` [PATCH (mtd-www) 4/7] nand-data: update MT29F8G08AB--- device IDs Angus CLARK
2012-01-07  3:26   ` Brian Norris
2012-01-05 16:13 ` [PATCH (mtd-www) 5/7] nand-data: add columns to the table Angus CLARK
2012-01-09 19:38   ` Brian Norris
2012-01-10 11:59     ` Angus CLARK
2012-01-13 21:35       ` Brian Norris
2012-01-05 16:13 ` [PATCH (mtd-www) 6/7] nand-data: expand Samsung "K9XDG08U5D" devices Angus CLARK
2012-01-09 19:43   ` Brian Norris
2012-01-05 16:14 ` [PATCH (mtd-www) 7/7] nand-data: add devices Angus CLARK
2012-01-07  3:06 ` [PATCH (mtd-www) 1/7] nand-data: updates to S30ML-P devices Brian Norris
2012-01-07 15:14 ` Artem Bityutskiy

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:6929691 dfblob:5bde226 )
 OR (
bs:"[PATCH (mtd-www) 2/7] nand-data: rename duplicate Numonyx NAND01G devices as 'Rev C'" )
	(help)

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=1325780040-19809-2-git-send-email-angus.clark@st.com \
    --to=angus.clark@st.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