aboutsummaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorzwelch <zwelch@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-06-16 12:17:12 +0000
committerzwelch <zwelch@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-06-16 12:17:12 +0000
commit491083a248a24c4b7d246e8f2c73b8ba1542d233 (patch)
treed4939150b5ada95212fcd44187a60905c3535fad /TODO
parent0de478618a048dc5abd0d54f878721d7e2901eac (diff)
downloadriscv-openocd-491083a248a24c4b7d246e8f2c73b8ba1542d233.zip
riscv-openocd-491083a248a24c4b7d246e8f2c73b8ba1542d233.tar.gz
riscv-openocd-491083a248a24c4b7d246e8f2c73b8ba1542d233.tar.bz2
David Brownell <david-b@pacbell.net>:
Tighten error handling on TAP enable/disable paths a bit: - Don't enable/disable unless it's necessary. Those event handlers could have nasty side effects... - Don't *succeed* enables/disables if there was no code which could have implemented that action. This prevents bugs like wrongly acting as if the scan chain changed. - Minor whitespace cleanup in enable/disable command code. The big problem is still the lack of code to verify scan chains were actually updated as requested; this adds a comment on that. I suspect the best we can do near term will be to verify IDCODE. git-svn-id: svn://svn.berlios.de/openocd/trunk@2250 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'TODO')
0 files changed, 0 insertions, 0 deletions