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>

diff --git a/doc/openocd.texi b/doc/openocd.texi
index 3781a398902dbd2f70c215f2782fd0d8fd6832c4..425e4393d81099d5c492d491f55287d33112575e 100644 (file)
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -3726,17 +3726,6 @@ The components of a dotted name should follow ``C'' symbol
 name rules: start with an alphabetic character, then numbers
 and underscores are OK; while others (including dots!) are not.
 
 name rules: start with an alphabetic character, then numbers
 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
 
 @c shouldn't this be(come) a {Config Command}?
 @section TAP Declaration Commands
 
 @c shouldn't this be(come) a {Config Command}?