public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Colin Cross <colin@mit.edu>
To: linux-mtd@lists.infradead.org
Subject: Jedec probe for strange 28F800B3 chips (patch)
Date: 08 May 2002 17:05:40 -0400	[thread overview]
Message-ID: <1020891940.2172.32.camel@sycamore.mit.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

I'm working on an embedded system that has two Flash chips labeled
28F800B3-10BD.  The Intel datasheets say they should have an identifier
of 0x8893 (which matches jedec_probe.c), but they report an identifier
of 0x889D.  I found one errata datasheet that says the correct
identifier for these chips is in fact 0x889D.  However, the block map of
this chip is completely different from the one described in the
datasheets.  It has 1 16kB block, 2 8kB blocks, 1 96kB, and 7 128kB
blocks.  This matches the block map for some other random Intel 8Mb
flash chip, but I can't find any datasheets that give this block map and
identifier together.  I've added these chips to jedec_probe.c, and they
work fine once added, but I'm at a loss as to why these chips don't
agree with the datasheets.  Can anyone offer any insight?  Does anyone
have 28F800B3 chips that follow the datasheet?  I've attached a patch
that adds support for them, but I'm not sure what to call them (Intel
28F800B3B version 2? for now).

[-- Attachment #2: jedec_probe_patch.txt --]
[-- Type: text/plain, Size: 1176 bytes --]

--- /home/colin/src/arm/mtd/mtd/drivers/mtd/chips/jedec_probe.c	Thu Apr 25 08:03:18 2002
+++ jedec_probe.c	Mon Apr 29 21:39:54 2002
@@ -66,6 +66,8 @@
 #define I28F008B3B	0x00d3
 #define I28F800B3T	0x8892
 #define I28F800B3B	0x8893
+#define I28F800B3T2	0x889C
+#define I28F800B3B2	0x889D
 #define I28F016S3	0x00aa
 #define I28F016B3T	0x00d0
 #define I28F016B3B	0x00d1
@@ -441,6 +399,32 @@
 		}
 	}, {
 		mfr_id:			MANUFACTURER_INTEL,
+		dev_id:			I28F800B3B2,
+		name:			"Intel 28F800B3B version 2?",
+		DevSize:		SIZE_1MiB,
+		CmdSet:			P_ID_INTEL_STD,
+		NumEraseRegions:	4,
+		regions: {
+			ERASEINFO(0x04000, 1),
+			ERASEINFO(0x02000, 2),
+			ERASEINFO(0x18000, 1),
+			ERASEINFO(0x20000, 7),
+		}
+	}, {
+		mfr_id:			MANUFACTURER_INTEL,
+		dev_id:			I28F800B3T2,
+		name:			"Intel 28F800B3T version 2?",
+		DevSize:		SIZE_1MiB,
+		CmdSet:			P_ID_INTEL_STD,
+		NumEraseRegions:	4,
+		regions: {
+			ERASEINFO(0x20000, 7),
+			ERASEINFO(0x18000, 1),
+			ERASEINFO(0x02000, 2),
+			ERASEINFO(0x04000, 1),
+		}
+	}, {
+		mfr_id:			MANUFACTURER_INTEL,
 		dev_id:			I28F016B3B,
 		name:			"Intel 28F016B3B",
 		DevSize:		SIZE_2MiB,

             reply	other threads:[~2002-05-08 21:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-08 21:05 Colin Cross [this message]
2002-05-08 22:34 ` Jedec probe for strange 28F800B3 chips (patch) Gregg C Levine
  -- strict thread matches above, loose matches on Subject: below --
2002-05-24 21:56 Conley, Christopher

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=1020891940.2172.32.camel@sycamore.mit.edu \
    --to=colin@mit.edu \
    --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