summaryrefslogtreecommitdiff
path: root/dummyflasher.c
diff options
context:
space:
mode:
authorhailfinger <hailfinger@2b7e53f0-3cfb-0310-b3e9-8179ed1497e1>2009-05-11 14:40:31 +0000
committerhailfinger <hailfinger@2b7e53f0-3cfb-0310-b3e9-8179ed1497e1>2009-05-11 14:40:31 +0000
commitd45ed17ef3419d1c2b51c9d243bb37c3ad53cce0 (patch)
tree4b6fb8163f074056ff12d1f3d28cd911dad2aaa4 /dummyflasher.c
parentc2a4234f8c00507eb7bfc638da33d98e4c91de5a (diff)
downloadflashrom-d45ed17ef3419d1c2b51c9d243bb37c3ad53cce0.tar.gz
When flashrom JEDEC code sends the ID command to the chip, it expects to
see IDs in the default flash location. However, sometimes the chip does not react to the ID command, either because it doesn't understand the command or because the command never reached it. One way to detect this is to compare ID output with flash chip contents for the same location. If they are identical, there is a high chance you're not actually seeing ID output. Warn the user in that case. This patch helps a lot when a chip is not recognized and we want to check if the probe responses are real IDs or just random flash chip contents. This should probably be added to all probe functions, but probe_jedec is called for all sizes and thus flashrom will check this condition at least once per size, making sure we can cross-match the warning. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by: FENG Yu Ning <fengyuning1984@gmail.com> git-svn-id: https://code.coreboot.org/svn/flashrom/trunk@494 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
Diffstat (limited to 'dummyflasher.c')
0 files changed, 0 insertions, 0 deletions