summaryrefslogtreecommitdiffstats
path: root/spi.h
diff options
context:
space:
mode:
authorCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>2008-11-28 01:25:00 +0000
committerCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>2008-11-28 01:25:00 +0000
commit14e50ac12310eac97f64ee8d6cb17dfb6407259b (patch)
treedb1512123838cee8ce82f11fb61def54898b073f /spi.h
parent92a54ca0300dd6e0f9773a4313ab489df79020c7 (diff)
downloadast2050-flashrom-14e50ac12310eac97f64ee8d6cb17dfb6407259b.zip
ast2050-flashrom-14e50ac12310eac97f64ee8d6cb17dfb6407259b.tar.gz
Flashrom already has the following probe functions
- probe_spi_rdid with opcode 0x9f, usually 3 bytes ID - probe_spi_res with opcode 0xab, usually 1 byte ID We are missing the following probe function: - probe_spi_rems with opcode 0x90, usually 2 bytes ID RDID provides best specifity (manufacturer, device class and device) and RES is supported by quite a few old chips. However, RES only returns one byte and there are multiple flash chips with different sizes on the market and all of them have the same RES ID. REMS is from the same age as RES, but it provides a manufacturer and a device ID. It is therefore on par with the probing for parallel flash chips and specific enough. The order in which chips should be detected is as follows: 1. RDID 2. REMS 3. RES Corresponding to flashrom svn r349 and coreboot v2 svn r3775. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by: Peter Stuge <peter@stuge.se>
Diffstat (limited to 'spi.h')
-rw-r--r--spi.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/spi.h b/spi.h
index 54c71fc..c096dce 100644
--- a/spi.h
+++ b/spi.h
@@ -29,6 +29,11 @@
#define JEDEC_RDID_OUTSIZE 0x01
#define JEDEC_RDID_INSIZE 0x03
+/* Read Electronic Manufacturer Signature */
+#define JEDEC_REMS 0x90
+#define JEDEC_REMS_OUTSIZE 0x04
+#define JEDEC_REMS_INSIZE 0x02
+
/* Read Electronic Signature */
#define JEDEC_RES 0xab
#define JEDEC_RES_OUTSIZE 0x04
OpenPOWER on IntegriCloud