summaryrefslogtreecommitdiffstats
path: root/chipdrivers.h
diff options
context:
space:
mode:
authorMichael Karcher <flashrom@mkarcher.dialup.fu-berlin.de>2011-04-14 23:43:19 +0000
committerMichael Karcher <flashrom@mkarcher.dialup.fu-berlin.de>2011-04-14 23:43:19 +0000
commit4b177369854b0f1b0f5769b809f2cf1b0ea4f347 (patch)
tree13f79018dc1bfb1da97f9b4fbd460e3e9448eaa3 /chipdrivers.h
parent2842db315de428fca28db6bfae0585fe602e41c0 (diff)
downloadast2050-flashrom-4b177369854b0f1b0f5769b809f2cf1b0ea4f347.zip
ast2050-flashrom-4b177369854b0f1b0f5769b809f2cf1b0ea4f347.tar.gz
Remove erase_chip_stm50flw0x0x
As the comment indicates, that function is not a chip erase function at all, but a function calling a block eraser in a loop. So it adds no extra value to what we already have in the block_eraser infrastructure. Furthermore, that function assumes a uniform sector size layout, but is referenced from flash chip with non-uniform sector size layout, which is just wrong. Corresponding to flashrom svn r1287. Signed-off-by: Michael Karcher <flashrom@mkarcher.dialup.fu-berlin.de> Acked-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Diffstat (limited to 'chipdrivers.h')
-rw-r--r--chipdrivers.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/chipdrivers.h b/chipdrivers.h
index c01ab7a..2c1cd8b 100644
--- a/chipdrivers.h
+++ b/chipdrivers.h
@@ -128,7 +128,6 @@ int probe_w29ee011(struct flashchip *flash);
/* stm50flw0x0x.c */
int erase_sector_stm50flw0x0x(struct flashchip *flash, unsigned int block, unsigned int blocksize);
-int erase_chip_stm50flw0x0x(struct flashchip *flash, unsigned int addr, unsigned int blocklen);
int unlock_stm50flw0x0x(struct flashchip *flash);
#endif /* !__CHIPDRIVERS_H__ */
OpenPOWER on IntegriCloud