diff options
author | Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> | 2009-05-11 14:40:31 +0000 |
---|---|---|
committer | Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> | 2009-05-11 14:40:31 +0000 |
commit | 8130f2d3ec2f7c32876d470edffbe44394d84d16 (patch) | |
tree | 4b6fb8163f074056ff12d1f3d28cd911dad2aaa4 /layout.c | |
parent | 1455b2baea9f4379086cabf1dcc1388c478c745c (diff) | |
download | flashrom-8130f2d3ec2f7c32876d470edffbe44394d84d16.tar.gz flashrom-8130f2d3ec2f7c32876d470edffbe44394d84d16.tar.bz2 flashrom-8130f2d3ec2f7c32876d470edffbe44394d84d16.zip |
Check probing results for flash contents
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.
Corresponding to flashrom svn r494.
Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Acked-by: FENG Yu Ning <fengyuning1984@gmail.com>
Diffstat (limited to 'layout.c')
0 files changed, 0 insertions, 0 deletions