diff options
author | Stu Grossman <grossman@cygnus> | 1992-10-23 08:50:19 +0000 |
---|---|---|
committer | Stu Grossman <grossman@cygnus> | 1992-10-23 08:50:19 +0000 |
commit | 6446b7a4b2fbd7cdeb52720c23a2f64c72c4f417 (patch) | |
tree | b28aba7eac55c460e73fead99e45d39d08f48691 /gdb/doc | |
parent | 5f5be54ce89622dec85bc6a598e426a7d2a52a4d (diff) | |
download | gdb-6446b7a4b2fbd7cdeb52720c23a2f64c72c4f417.zip gdb-6446b7a4b2fbd7cdeb52720c23a2f64c72c4f417.tar.gz gdb-6446b7a4b2fbd7cdeb52720c23a2f64c72c4f417.tar.bz2 |
Remove refs to UDI for now.
Diffstat (limited to 'gdb/doc')
-rw-r--r-- | gdb/doc/gdb.texinfo | 7 | ||||
-rw-r--r-- | gdb/doc/gdbinv-m.m4.in | 1 | ||||
-rw-r--r-- | gdb/doc/gdbinv-s.m4.in | 18 |
3 files changed, 0 insertions, 26 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index d439369..b5695ac 100644 --- 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 13738b0..95852b5 100644 --- 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 864cc18..6a09530 100644 --- 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__) |