summaryrefslogtreecommitdiffstats
path: root/spi.c
diff options
context:
space:
mode:
authorCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>2012-02-16 20:31:25 +0000
committerCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>2012-02-16 20:31:25 +0000
commitb428e97cb1fcd8937b5a2cb75317acc4d4e4390a (patch)
treef82c61c4dfb3dec5c7d1c6f061fb65cc0d791028 /spi.c
parent5b5547126d9e80ce6e9c8572b7eb810990618b57 (diff)
downloadast2050-flashrom-b428e97cb1fcd8937b5a2cb75317acc4d4e4390a.zip
ast2050-flashrom-b428e97cb1fcd8937b5a2cb75317acc4d4e4390a.tar.gz
Reenable forced read
Forced read functionality was disabled when programmer registration was merged in r1475. We now support registering more than one controller at once for each bus type. This can happen e.g. if one SPI controller has an attached flash chip and one controller doesn't. In such a case we rely on the probe mechanism to find exactly one chip, and the probe mechanism will remember which controller/bus the flash chip is attached to. A forced read does not have the luxury of knowing which compatible controller to use, so this case is handled by always picking the first one. That may or may not be the correct one, but there is no way (yet) to specify which controller a flash chip is attached to. Corresponding to flashrom svn r1496. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by: Stefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
Diffstat (limited to 'spi.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud