summaryrefslogtreecommitdiffstats
path: root/arch/mips/kernel
diff options
context:
space:
mode:
authorRalf Baechle <ralf@linux-mips.org>2000-12-04 04:04:09 +0000
committerRalf Baechle <ralf@linux-mips.org>2000-12-04 04:04:09 +0000
commit074da8c3f230190b4a00177ff781f0a76d8b0dfe (patch)
treef62c562c8c324258f0c79cea9b99172783212827 /arch/mips/kernel
parent1fbefa026d5a271ed014b1bb730de8de06ca89d5 (diff)
EV64120 support. From Steve Johnson.
Diffstat (limited to 'arch/mips/kernel')
-rw-r--r--arch/mips/kernel/gdb-stub.c55
-rw-r--r--arch/mips/kernel/setup.c5
2 files changed, 60 insertions, 0 deletions
diff --git a/arch/mips/kernel/gdb-stub.c b/arch/mips/kernel/gdb-stub.c
index ceb678bb3..f86da1881 100644
--- a/arch/mips/kernel/gdb-stub.c
+++ b/arch/mips/kernel/gdb-stub.c
@@ -64,6 +64,61 @@
* Host: Reply:
* $m0,10#2a +$00010203040506070809101112131415#42
*
+ *
+ * ==============
+ * MORE EXAMPLES:
+ * ==============
+ *
+ * For reference -- the following are the steps that one
+ * company took (RidgeRun Inc) to get remote gdb debugging
+ * going. In this scenario the host machine was a PC and the
+ * target platform was a Galileo EVB64120A MIPS evaluation
+ * board.
+ *
+ * Step 1:
+ * First download gdb-5.0.tar.gz from the internet.
+ * and then build/install the package.
+ *
+ * Example:
+ * $ tar zxf gdb-5.0.tar.gz
+ * $ cd gdb-5.0
+ * $ ./configure --target=mips-linux-elf
+ * $ make
+ * $ install
+ * $ which mips-linux-elf-gdb
+ * /usr/local/bin/mips-linux-elf-gdb
+ *
+ * Step 2:
+ * Configure linux for remote debugging and build it.
+ *
+ * Example:
+ * $ cd ~/linux
+ * $ make menuconfig <go to "Kernel Hacking" and turn on remote debugging>
+ * $ make dep; make vmlinux
+ *
+ * Step 3:
+ * Download the kernel to the remote target and start
+ * the kernel running. It will promptly halt and wait
+ * for the host gdb session to connect. It does this
+ * since the "Kernel Hacking" option has defined
+ * CONFIG_REMOTE_DEBUG which in turn enables your calls
+ * to:
+ * set_debug_traps();
+ * breakpoint();
+ *
+ * Step 4:
+ * Start the gdb session on the host.
+ *
+ * Example:
+ * $ mips-linux-elf-gdb vmlinux
+ * (gdb) set remotebaud 115200
+ * (gdb) target remote /dev/ttyS1
+ * ...at this point you are connected to
+ * the remote target and can use gdb
+ * in the normal fasion. Setting
+ * breakpoints, single stepping,
+ * printing variables, etc.
+ *
*/
#include <linux/string.h>
diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
index 58d834a43..44d0f0daf 100644
--- a/arch/mips/kernel/setup.c
+++ b/arch/mips/kernel/setup.c
@@ -430,6 +430,11 @@ void __init setup_arch(char **cmdline_p)
ev96100_setup();
break;
#endif
+#ifdef CONFIG_MIPS_EV64120
+ case MACH_GROUP_GALILEO:
+ ev64120_setup();
+ break;
+#endif
default:
panic("Unsupported architecture");
}