Remove refs to UDI for now.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index d4393694f88ffc828276294821d5634c17aa3d2f..b5695ac8535ddd818800d9e60a6624f39a368fd2 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -6583,13 +6583,6 @@ Remote PC-resident AMD EB29K board, attached over serial lines.
 name of the program to be debugged, as it appears to DOS on the PC.
 @xref{EB29K Remote, ,_GDBN__ with a Remote EB29K}.
 
-@item target udi
-@kindex target udi
-@cindex UDI interface to 29K
-@cindex AMD UDI-29K
-Remote AMD 29K board, attached over the AMD ``Universal Debug
-Interface'', a protocol based on TCP/IP.  @xref{UDI29K Remote,,_GDBN__
-and the UDI 29K protocol}.
 _fi__(_AMD29K__)
 _if__(_H8__)
 @item target hms

diff --git a/gdb/doc/gdbinv-m.m4.in b/gdb/doc/gdbinv-m.m4.in
index 13738b03e6d7d3ce0afdb4689b9ec22ea46aee0d..95852b5556508984a5d8a3600db110791a18e6d0 100644 (file)
--- a/gdb/doc/gdbinv-m.m4.in
+++ b/gdb/doc/gdbinv-m.m4.in
@@ -10,7 +10,6 @@ _if__(_I960__)
 _fi__(_I960__)
 _if__(_AMD29K__)
 * EB29K Remote::               _GDBN__ with a remote EB29K
-* UDI29K Remote::               _GDBN__ and the UDI 29K protocol
 _fi__(_AMD29K__)
 _if__(_VXWORKS__)
 * VxWorks Remote::             _GDBN__ and VxWorks

diff --git a/gdb/doc/gdbinv-s.m4.in b/gdb/doc/gdbinv-s.m4.in
index 864cc186ce7d494d4c9f3470d9820405e4f84c2f..6a0953022b2597c99741eb0cc31ca2bb3e4e0fb9 100644 (file)
--- a/gdb/doc/gdbinv-s.m4.in
+++ b/gdb/doc/gdbinv-s.m4.in
@@ -628,24 +628,6 @@ of the commands sent to it.  Running @samp{tail -f} on this file in
 another window often helps to understand trouble with @code{EBMON}, or
 unexpected events on the PC side of the connection.
 
-@node UDI29K Remote
-@subsection _GDBN__ and the UDI 29K protocol
-
-If your 29K development system supports the UDI (``Universal Debug
-Interface'') protocol, using _GDBN__ is almost transparent.  UDI is a
-TCP/IP based protocol.  On some 29K development systens that do not
-support TCP/IP directly, however, the manufacturer supplies an interface
-adapter daemon, which translates UDI to whatever communications
-interface---typically a serial port---is available.
-
-Please see the manufacturer's documentation for your 29K system for how
-to set up the UDI connection for your hardware.
-
-Once the UDI connection is established, use @samp{target udi} from _GDBN__
-to start using it.  All the usual facilities of _GDBN__ are immediately
-available: use @code{load} to get your program to the board,
-@code{breakpoint} to say where to stop, @code{run} to start the program,
-and so on.
 _fi__(_AMD29K__)
 
 _if__(_ST2000__)