path: root/flash.h
diff options
authorCarl-Daniel Hailfinger <>2008-11-28 01:25:00 +0000
committerCarl-Daniel Hailfinger <>2008-11-28 01:25:00 +0000
commit14e50ac12310eac97f64ee8d6cb17dfb6407259b (patch)
treedb1512123838cee8ce82f11fb61def54898b073f /flash.h
parent92a54ca0300dd6e0f9773a4313ab489df79020c7 (diff)
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 <> Acked-by: Peter Stuge <>
Diffstat (limited to 'flash.h')
1 files changed, 1 insertions, 0 deletions
diff --git a/flash.h b/flash.h
index 9f6a862..d1e417f 100644
--- a/flash.h
+++ b/flash.h
@@ -449,6 +449,7 @@ extern char *lb_part, *lb_vendor;
/* spi.c */
int probe_spi_rdid(struct flashchip *flash);
int probe_spi_rdid4(struct flashchip *flash);
+int probe_spi_rems(struct flashchip *flash);
int probe_spi_res(struct flashchip *flash);
int spi_command(unsigned int writecnt, unsigned int readcnt,
const unsigned char *writearr, unsigned char *readarr);
OpenPOWER on IntegriCloud