aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc/gdbinv-s.texi
diff options
context:
space:
mode:
authorFred Fish <fnf@specifix.com>1993-03-29 23:38:30 +0000
committerFred Fish <fnf@specifix.com>1993-03-29 23:38:30 +0000
commitd7d35f004c9c506c0b3f7002d96bad37bb492411 (patch)
tree1be5d01f55afb1b6446607159ef3e0dc9098d440 /gdb/doc/gdbinv-s.texi
parente5c007603f1d64f2f5722cb6f79227b5fd0f9350 (diff)
downloadgdb-d7d35f004c9c506c0b3f7002d96bad37bb492411.zip
gdb-d7d35f004c9c506c0b3f7002d96bad37bb492411.tar.gz
gdb-d7d35f004c9c506c0b3f7002d96bad37bb492411.tar.bz2
* config/a29k/tm-a29k.h: Renamed from config/a29k/tm-29k.h.
* a29k-pinsn.c: Renamed from am29k-pinsn.c. * a29k-tdep.c: Renamed from am29k-tdep.c. * remote-eb.c, config/a29k/tm-ultra3.h: Include renamed tm-a29k.h. * remote-monitor.c, remote-st2000.c, config/a29k/{nm-ultra3.h, tm-a29k.h, xm-ultra3.h}, config/romp/rtbsd.mh, doc/gdbinv-s.texi, testsuite/gdb.t15/funcargs.exp, testsuite/gdb.t17/callfuncs.exp: Map '29k' to 'a29k'. * config/a29k/{a29k-kern.mt, a29k-udi.mt, a29k.mt, ultra3.mt} (TDEPFILES): Use renamed a29k-pinsn.o and a29k-tdep.o. * config/a29k/{a29k-udi.mt, a29k.mt} (TM_FILE): Use renamed tm-a29k.h. * config/a29k/a29k-udi.mt (MT_CFLAGS): Remove TARGET_AM29K define that does not appear anywhere else in the gdb source tree. * doc/gdbinit.texinfo: Document renaming of tm-29k.h to tm-a29k.h.
Diffstat (limited to 'gdb/doc/gdbinv-s.texi')
-rw-r--r--gdb/doc/gdbinv-s.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/gdb/doc/gdbinv-s.texi b/gdb/doc/gdbinv-s.texi
index e3c625a..a94fa24 100644
--- a/gdb/doc/gdbinv-s.texi
+++ b/gdb/doc/gdbinv-s.texi
@@ -451,19 +451,19 @@ a break is detected.
@cindex UDI
@cindex AMD29K via UDI
@value{GDBN} supports AMD's UDI (``Universal Debugger Interface'')
-protocol for debugging the 29k processor family. To use this
+protocol for debugging the a29k processor family. To use this
configuration with AMD targets running the MiniMON monitor, you need the
program @code{MONTIP}, available from AMD at no charge. You can also
-use @value{GDBN} with the UDI conformant 29k simulator program
+use @value{GDBN} with the UDI conformant a29k simulator program
@code{ISSTIP}, also available from AMD.
@table @code
@item target udi @var{keyword}
@kindex udi
-Select the UDI interface to a remote 29K board or simulator, where
+Select the UDI interface to a remote a29k board or simulator, where
@var{keyword} is an entry in the AMD configuration file @file{udi_soc}.
This file contains keyword entries which specify parameters used to
-connect to 29k targets. If the @file{udi_soc} file is not in your
+connect to a29k targets. If the @file{udi_soc} file is not in your
working directory, you must set the environment variable @samp{UDICONF}
to its pathname.
@end table