interesting
/
riscv-openocd
mirror of https://github.com/riscv/riscv-openocd.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Remove obsolete tip referring to 2010 removal of TAP numbers. 

Remove a tip describing the discouraged use of TAP numbers, and how
these numbers would be removed by mid-2010.

Change-Id: Iebe7e2e4a0f8e1f18a91d7935588dd9ced2b398d
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Reviewed-on: http://openocd.zylin.com/1862
Tested-by: jenkins
Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>
This commit is contained in:
Robert P. J. Day 2014-01-11 04:42:35 -05:00 committed by Spencer Oliver
parent 1520e37719
commit acc67744c0
1 changed files with 0 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/openocd.texi
View File

@ -3726,17 +3726,6 @@ The components of a dotted name should follow ``C'' symbol
name rules: start with an alphabetic character, then numbers name rules: start with an alphabetic character, then numbers
and underscores are OK; while others (including dots!) are not. and underscores are OK; while others (including dots!) are not.
@quotation Tip
In older code, JTAG TAPs were numbered from 0..N.
This feature is still present.
However its use is highly discouraged, and
should not be relied on; it will be removed by mid-2010.
Update all of your scripts to use TAP names rather than numbers,
by paying attention to the runtime warnings they trigger.
Using TAP numbers in target configuration scripts prevents
reusing those scripts on boards with multiple targets.
@end quotation
@section TAP Declaration Commands @section TAP Declaration Commands
@c shouldn't this be(come) a {Config Command}? @c shouldn't this be(come) a {Config Command}?