Message ID | 1323173269-19931-6-git-send-email-angus.clark@st.com |
---|---|
State | New, archived |
Headers | show |
On Tue, Dec 6, 2011 at 4:07 AM, Angus CLARK <angus.clark@st.com> wrote:
> Change Samsung "K9XDG08U5D" to "K9MDG08U5D".
According to my data sheet, all the following are available:
K9LBG08U0D
K9HCG08U1D
K9MDG08U5D
K9PDGZ8U5D
K9PDG08U5D
While they use "K9XDG08U5D" to cover the last 3 chips with the same ID
under the "Read ID" section, with `X' as a wildcard character. So it
should match K9MDG08U5D, K9PDG08U5D, and K9PDGZ8U5D.
Any of the following covers the chips close enough (see other message
regarding wildcards):
K9xDG08U5D
K9xDGx8U5D
K9-DG08U5D
K9-DG-8U5D
Hi Brian, On 12/07/2011 07:38 PM, Brian Norris wrote: > On Tue, Dec 6, 2011 at 4:07 AM, Angus CLARK <angus.clark@st.com> wrote: >> Change Samsung "K9XDG08U5D" to "K9MDG08U5D". > > According to my data sheet, all the following are available: > > K9LBG08U0D > K9HCG08U1D > K9MDG08U5D > K9PDGZ8U5D > K9PDG08U5D > > While they use "K9XDG08U5D" to cover the last 3 chips with the same ID > under the "Read ID" section, with `X' as a wildcard character. So it > should match K9MDG08U5D, K9PDG08U5D, and K9PDGZ8U5D. > Ah, that makes sense, or at least for the K9MDG08U5D and K9PDG08U5D devices. I can't find much information relating to K9PDGZ8U5D - the part number decoder I have suggests this would be 'SSD' technology (rather than x8 or x16). Can you shed any light on this? I see the datasheet uses capital 'X' as the wildcard, but perhaps lower-case 'x' (or '-' as you have suggested in other replies) would be less confusing. Also, although the K9MDG08U5D and K9PDG08U5D devices are equivalent with respect to the current columns in the table, one of the later patches I submitted added the "I/O interface" column: this is "Single" for the K9MDG08U5D device and "Dual" for the K9PDG08U5D device. Would you object to us keeping this patch as is, and I will add K9PDG08U5D as a separate device, with "Dual" I/O? Cheers, Angus
On Fri, Dec 9, 2011 at 3:38 AM, Angus CLARK <angus.clark@st.com> wrote: > On 12/07/2011 07:38 PM, Brian Norris wrote: >> On Tue, Dec 6, 2011 at 4:07 AM, Angus CLARK <angus.clark@st.com> wrote: >>> Change Samsung "K9XDG08U5D" to "K9MDG08U5D". >> >> According to my data sheet, all the following are available: >> >> K9LBG08U0D >> K9HCG08U1D >> K9MDG08U5D >> K9PDGZ8U5D >> K9PDG08U5D >> >> While they use "K9XDG08U5D" to cover the last 3 chips with the same ID >> under the "Read ID" section, with `X' as a wildcard character. So it >> should match K9MDG08U5D, K9PDG08U5D, and K9PDGZ8U5D. >> > > Ah, that makes sense, or at least for the K9MDG08U5D and K9PDG08U5D devices. I > can't find much information relating to K9PDGZ8U5D - the part number decoder I > have suggests this would be 'SSD' technology (rather than x8 or x16). Can you > shed any light on this? Not really. I've never seen the K9PDGZ8U5D, and judging by the 'SSD', it probably wouldn't fit into our classifications too well. > I see the datasheet uses capital 'X' as the wildcard, but perhaps lower-case 'x' > (or '-' as you have suggested in other replies) would be less confusing. I'd go with lowercase 'x' > Also, although the K9MDG08U5D and K9PDG08U5D devices are equivalent with respect > to the current columns in the table, one of the later patches I submitted added > the "I/O interface" column: this is "Single" for the K9MDG08U5D device and > "Dual" for the K9PDG08U5D device. > > Would you object to us keeping this patch as is, and I will add K9PDG08U5D as a > separate device, with "Dual" I/O? No, I guess not. That means we leave out K9PDGZ8U5D, which is fine with me. Brian
diff --git a/nand-data/nanddata.csv b/nand-data/nanddata.csv index 53b9a94..cd75572 100644 --- a/nand-data/nanddata.csv +++ b/nand-data/nanddata.csv @@ -128,7 +128,7 @@ "Samsung","K9LAG08U1A","0xEC","0xD3","0xECD314A564",2048,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",FALSE,FALSE,TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE, "Samsung","K9LBG08U0D","0xEC","0xD7","0xECD7D5293841",4096,4096,218,"512 KB","x8","N/A","Last page (1st byte in OOB = non FFh)",FALSE,TRUE,FALSE,TRUE,FALSE,"8-bit/512-byte (correction)",2,6,"Extended ID decode (Samsung)",TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE, "Samsung","K9HCG08U1D","0xEC","0xD7","0xECD7D5293841",8192,4096,218,"512 KB","x8","N/A","Last page (1st byte in OOB = non FFh)",FALSE,TRUE,FALSE,TRUE,FALSE,"8-bit/512-byte (correction)",2,6,"Extended ID decode (Samsung)",FALSE,FALSE,TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE, -"Samsung","K9XDG08U5D","0xEC","0xD7","0xECD7D5293841",16384,4096,218,"512 KB","x8","N/A","Last page (1st byte in OOB = non FFh)",FALSE,TRUE,FALSE,TRUE,FALSE,"8-bit/512-byte (correction)",2,6,"Extended ID decode (Samsung)",FALSE,FALSE,TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE, +"Samsung","K9MDG08U5D","0xEC","0xD7","0xECD7D5293841",16384,4096,218,"512 KB","x8","N/A","Last page (1st byte in OOB = non FFh)",FALSE,TRUE,FALSE,TRUE,FALSE,"8-bit/512-byte (correction)",2,6,"Extended ID decode (Samsung)",FALSE,FALSE,TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE, "Numonyx","NAND08GW3F2B","0x20","0xD3","0x20D390152441",1024,2048,64,"128 KB","x8","N/A","1st page (1st or 6th byte in OOB = non FFh)",FALSE,FALSE,FALSE,TRUE,TRUE,"1-bit/512-byte",1,6,"Extended ID decode",TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE,TRUE, "Samsung","K9K8G08U0B","0xEC","0xDC","0xECDC519558",1024,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",FALSE,FALSE,TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE, "Samsung","K9WAG08U1B","0xEC","0xDC","0xECDC519558",2048,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",FALSE,FALSE,TRUE,FALSE,TRUE,TRUE,TRUE,TRUE,TRUE,
Change Samsung "K9XDG08U5D" to "K9MDG08U5D". Signed-off-by: Angus Clark <angus.clark@st.com> --- nand-data/nanddata.csv | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)