* doc/gdb.texinfo, doc/gdbinv-m.m4.in, doc/gdbinv-s.m4.in: first

pass at doc for two new remote targets---29K using UDI, and Tandem
	ST2000 using STDBUG.

	* doc/all.m4, doc/none.m4: new m4 switch, _ST2000__

	* doc/all.m4: turn on H8/300 stuff for generic manual

gdb/doc/all.m4

@@ -8,11 +8,12 @@ _define__(<_COFF__>,<1>)
 _define__(<_ELF__>,<1>)
 
 _define__(<_AMD29K__>,<1>)
-_define__(<_H8__>,<0>)           Include this when it's stable.
+_define__(<_H8__>,<1>)           Include this when it's stable.
 _define__(<_I80386__>,<1>)
 _define__(<_I960__>,<1>)
 _define__(<_M680X0__>,<1>)
 _define__(<_SPARC__>,<1>)
+_define__(<_ST2000__>,<1>)
 _define__(<_VAX__>,<1>)
 _define__(<_VXWORKS__>,<1>)
 

gdb/doc/gdb.texinfo

@@ -176,9 +176,9 @@ _if__(!_DOSHOST__)
 * Emacs::                       Using _GDBN__ under GNU Emacs
 _fi__(!_DOSHOST__)
 * _GDBN__ Bugs::                    Reporting bugs in _GDBN__
-_if__(!_H8__)
+_if__(_GENERIC__||!_H8__)
 * Renamed Commands::
-_fi__(!_H8__)
+_fi__(_GENERIC__||!_H8__)
 * Formatting Documentation::    How to format and print GDB documentation
 * Installing GDB::              Installing GDB
 * Copying::                     GNU GENERAL PUBLIC LICENSE
@@ -6511,8 +6511,15 @@ Remote PC-resident AMD EB29K board, attached over serial lines.
 @var{dev} is the serial device, as for @code{target remote};
 @var{speed} allows you to specify the linespeed; and @var{PROG} is the
 name of the program to be debugged, as it appears to DOS on the PC.
-@xref{EB29K Remote, ,GDB with a Remote EB29K}.
+@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
@@ -6531,6 +6538,16 @@ the name of the serial device to use for the connection, e.g.
 @file{/dev/ttya}.  @xref{i960-Nindy Remote, ,_GDBN__ with a Remote i960 (Nindy)}.
 
 _fi__(_I960__)
+_if__(_ST2000__)
+@item target st2000 @var{dev} @var{speed}
+@kindex target st2000
+A Tandem ST2000 phone switch, running Tandem's STDBUG protocol.  @var{dev}
+is the name of the device attached to the ST2000 serial line;
+@var{speed} is the communication line speed.  The arguments are not used
+if _GDBN__ is configured to connect to the ST2000 using TCP or Telnet.
+@xref{ST2000 Remote,,_GDBN__ with a Tandem ST2000}.
+
+_fi__(_ST2000__)
 _if__(_VXWORKS__)
 @item target vxworks @var{machinename}
 @kindex target vxworks

gdb/doc/gdbinv-m.m4.in

@@ -8,10 +8,14 @@ _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
 _fi__(_VXWORKS__)
+_if__(_ST2000__)
+* ST2000 Remote::               _GDBN__ with a Tandem ST2000
+_fi__(_ST2000__)
 _if__(_H8__)
 * Hitachi H8/300 Remote::       _GDBN__ and the Hitachi H8/300
 _fi__(_H8__)

gdb/doc/gdbinv-s.m4.in

@@ -622,8 +622,71 @@ current working directory, to help debug problems with the connection.
 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__)
+@node ST2000 Remote
+@subsection _GDBN__ with a Tandem ST2000
+
+To connect your ST2000 to the host system, see the manufacturer's
+manual.  Once the ST2000 is physically attached, you can run
+
+@example
+target st2000 @var{dev} @var{speed}
+@end example
+
+@noindent
+to establish it as your debugging environment.  
+
+The @code{load} and @code{attach} commands are @emph{not} defined for
+this target; you must load your program into the ST2000 as you normally
+would for standalone operation.  _GDBN__ will read debugging information
+(such as symbols) from a separate, debugging version of the program
+available on your host computer.
+@c FIXME!! This is terribly vague; what little content is here is
+@c basically hearsay.
+
+@cindex ST2000 auxiliary commands
+These auxiliary _GDBN__ commands are available to help you with the ST2000
+environment:
+
+@table @code
+@item st2000 @var{command}
+@kindex st2000 @var{cmd}
+@cindex STDBUG commands (ST2000)
+@cindex commands to STDBUG (ST2000)
+Send a @var{command} to the STDBUG monitor.  See the manufacturer's
+manual for available commands.
+
+@item connect
+@cindex connect (to STDBUG)
+Connect the controlling terminal to the STDBUG command monitor.  When
+you are done interacting with STDBUG, typing either of two character
+sequences will get you back to the _GDBN__ command prompt:
+@kbd{@key{RET}~.} (Return, followed by tilde and period) or
+@kbd{@key{RET}~@key{C-d}} (Return, followed by tilde and control-D).
+@end table
+_fi__(_ST2000__)
+
 _if__(_VXWORKS__)
 @node VxWorks Remote
 @subsection _GDBN__ and VxWorks

gdb/doc/none.m4

@@ -34,6 +34,7 @@ _define__(<_I80386__>,<0>)		starts out on.
 _define__(<_I960__>,<0>)
 _define__(<_M680X0__>,<0>)
 _define__(<_SPARC__>,<0>)
+_define__(<_ST2000__>,<0>)
 _define__(<_VAX__>,<0>)
 _define__(<_VXWORKS__>,<0>)