summaryrefslogtreecommitdiffstats
path: root/flash.h
diff options
context:
space:
mode:
authorCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>2008-11-27 22:48:48 +0000
committerCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>2008-11-27 22:48:48 +0000
commit92a54ca0300dd6e0f9773a4313ab489df79020c7 (patch)
tree873b9b570fd7b47fd5ff1aefea826c55e422ac71 /flash.h
parentebaffb6e51fcda2f3a337e86cbce5f5598c19367 (diff)
downloadast2050-flashrom-92a54ca0300dd6e0f9773a4313ab489df79020c7.zip
ast2050-flashrom-92a54ca0300dd6e0f9773a4313ab489df79020c7.tar.gz
Try RES even if RDID fails
The existing check in probe_spi_res() was right for SPI controllers which support all commands, but may not exist. For controllers which support only a subset of commands, it will fail in unexpected ways. Even if a command is supported by the controller, it may be unavailable if the controller is locked down. The new logic checks if RDID could be issued and its return values made sense (not 0xff 0xff 0xff). In that case, RES probing is not performed. Otherwise, we try RES. There is one drawback: If RDID returned unexpected values, we don't issue a RES probe. However, in that case we should try to match RDID anyway. Corresponding to flashrom svn r348 and coreboot v2 svn r3774. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by: FENG yu ning <fengyuning1984@gmail.com>
Diffstat (limited to 'flash.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud