diff options
author | David Brownell <dbrownell@users.sourceforge.net> | 2010-03-03 20:57:49 -0800 |
---|---|---|
committer | David Brownell <dbrownell@users.sourceforge.net> | 2010-03-03 20:57:49 -0800 |
commit | 5fdf9535cef7e43f6e99081b6d1f6bd682184803 (patch) | |
tree | 6d82b33625ae2358c0fc79b43e5227bb7b604602 /src/helper/replacements.c | |
parent | 99939c3c75f3bef44d4cd176e90a6c5fe8b833da (diff) | |
download | openocd_libswd-5fdf9535cef7e43f6e99081b6d1f6bd682184803.tar.gz openocd_libswd-5fdf9535cef7e43f6e99081b6d1f6bd682184803.tar.bz2 openocd_libswd-5fdf9535cef7e43f6e99081b6d1f6bd682184803.tar.xz openocd_libswd-5fdf9535cef7e43f6e99081b6d1f6bd682184803.zip |
NOR: invalidate cached state on target resume
The NOR infrastructure caches some per-sector state, but
it's not used much ... because the cache is not trustworthy.
This patch addresses one part of that problem, by ensuring
that state cached by NOR drivers gets invalidated once we
resume the target -- since targets may then modify sectors.
Now if we see sector protection or erase status marked as
anything other than "unknown", we should be able to rely
on that as being accurate. (That is ... if we assume the
drivers initialize and update this state correctly.)
Another part of that problem is that the cached state isn't
much used (being unreliable, it would have been unsafe).
Those issues can be addressed in later patches.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'src/helper/replacements.c')
0 files changed, 0 insertions, 0 deletions