[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

src/sys/arch/mvme88k typos



Yes I am aware these are not bugs per se, as mvme88k is not officially
supported, but I figured I would report them anyway...

Index: mvme88k/ddb/db_trace.c
===================================================================
RCS file: /cvs/src/sys/arch/mvme88k/ddb/db_trace.c,v
retrieving revision 1.26
diff -u -r1.26 db_trace.c
--- mvme88k/ddb/db_trace.c	2004/01/13 18:40:47	1.26
+++ mvme88k/ddb/db_trace.c	2004/01/29 21:08:36
@@ -799,7 +799,7 @@
 	 *   0 if this looks like neither.
 	 */
 	if ((ft = frame_is_sane(regs, 1)) == 0) {
-		(*pr)("Register frame 0x%x is suspicous; skipping trace\n", regs);
+		(*pr)("Register frame 0x%x is suspicious; skipping trace\n", regs);
 		return;
 	}
 
Index: mvme88k/dev/vs.c
===================================================================
RCS file: /cvs/src/sys/arch/mvme88k/dev/vs.c,v
retrieving revision 1.28
diff -u -r1.28 vs.c
--- mvme88k/dev/vs.c	2004/01/20 16:48:27	1.28
+++ mvme88k/dev/vs.c	2004/01/29 21:08:36
@@ -904,11 +904,11 @@
 	case CEVSB_ERR_BD:	/* Bad direction */
 		printf("%s: Bad Direction!\n", vs_name(sc));
 		break;
-	case CEVSB_ERR_NR:	/* Non-Recoverabl Error */
+	case CEVSB_ERR_NR:	/* Non-Recoverable Error */
 		printf("%s: Non-Recoverable error!\n", vs_name(sc));
 		break;
-	case CESVB_ERR_PANIC:	/* Board Painc!!! */
-		printf("%s: Board Painc!!!\n", vs_name(sc));
+	case CESVB_ERR_PANIC:	/* Board Panic!!! */
+		printf("%s: Board Panic!!!\n", vs_name(sc));
 		break;
 	default:
 		printf("%s: Uh oh!... Error 0x%x\n", vs_name(sc), ecode);
Index: mvme88k/mvme88k/eh.S
===================================================================
RCS file: /cvs/src/sys/arch/mvme88k/mvme88k/eh.S,v
retrieving revision 1.49
diff -u -r1.49 eh.S
--- mvme88k/mvme88k/eh.S	2004/01/29 00:41:23	1.49
+++ mvme88k/mvme88k/eh.S	2004/01/29 21:08:36
@@ -791,7 +791,7 @@
 	 * We just want to jump to "badaddr__return_nonzero" below.
 	 *
 	 * We don't worry about trashing R2 here because we're
-	 * jumping back to the function badaddr() where we're allowd
+	 * jumping back to the function badaddr() where we're allowed
 	 * to blast r2..r9 as we see fit.
 	 */
 
@@ -838,15 +838,15 @@
  * extern boolean_t badaddr(unsigned addr, unsigned len)
  *
  * Returns true (non-zero) if the given LEN bytes starting at ADDR are
- * not all currently accessable by the kernel.
+ * not all currently accessible by the kernel.
  *
- * If all LEN bytes starting at ADDR are accessable, zero is returned.
+ * If all LEN bytes starting at ADDR are accessible, zero is returned.
  *
  * Len may be be 1, 2, or 4.
  *
- * This is implementd by setting a special flag in SR1 before trying to access
+ * This is implemented by setting a special flag in SR1 before trying to access
  * the given address. If a data access exception is raised, the address
- * is inaccessable. The exception handler will notice the special CPU flag
+ * is inaccessible. The exception handler will notice the special CPU flag
  * and not try to swap the address in. Rather, it will return to
  * "badaddr__return_nonzero" in this routine so that we may return non-zero
  * to the calling routine.
@@ -1024,7 +1024,7 @@
 	 * FLAGS: CPU status flags
 	 *
 	 * immediate goal:
-	 *   An exception occured while enabling the FPU. Since r31
+	 *   An exception occurred while enabling the FPU. Since r31
 	 *   is the user's r31 while enabling the FPU, we had put
 	 *   our pcb pointer into SR3, so make room from
 	 *   there for our stack pointer.
@@ -1301,7 +1301,7 @@
 
 ASLOCAL(clear_FPi_ssbr_bit)
 	/*
-	 * Clear floatingpont-imprecise ssbr bits.
+	 * Clear floatingpoint-imprecise ssbr bits.
 	 * Also, save appropriate FPU control registers to the E.F.
 	 *
 	 * r1:  return address to calling exception handler
@@ -1546,7 +1546,7 @@
 	 *   FPU control registers, if appropriate.
 	 *   Exception SR3, if appropriate.
 	 *   Held temporarly in the exception frame:
-	 *   Return address to the calling excption handler.
+	 *   Return address to the calling exception handler.
 	 *
 	 * immediate goal:
 	 *   Do an RTE to restart the fpu and jump to "fpu_enable"
@@ -2369,7 +2369,7 @@
 	 * FLAGS: CPU status flags
 	 *
 	 * immediate goal:
-	 *   An exception occured while enabling the FPU. Since r31 is the
+	 *   An exception occurred while enabling the FPU. Since r31 is the
 	 *   user's r31 while enabling the FPU, we had put our pcb pointer
 	 *   into SR3, so make room from there for our stack pointer.
 	 *   We need to check if SR3 is the old stack pointer or the pointer
@@ -2572,8 +2572,8 @@
 	 *   Other data pipeline control registers, if appropriate.
 	 *   FPU control registers, if appropriate.
 	 *   Exception SR3, if appropriate.
-	 * Held temporarly in the exception frame:
-	 *   Return address to the calling excption handler.
+	 * Held temporarily in the exception frame:
+	 *   Return address to the calling exception handler.
 	 *
 	 * immediate goal:
 	 *   Do an RTE to restart the fpu and jump to "m88110_fpu_enable"
Index: mvme88k/mvme88k/trap.c
===================================================================
RCS file: /cvs/src/sys/arch/mvme88k/mvme88k/trap.c,v
retrieving revision 1.71
diff -u -r1.71 trap.c
--- mvme88k/mvme88k/trap.c	2004/01/29 00:41:23	1.71
+++ mvme88k/mvme88k/trap.c	2004/01/29 21:08:36
@@ -1167,7 +1167,7 @@
 		db_printf("\n[ERROR EXCEPTION (Bad News[tm]) frame %p]\n", frame);
 		db_printf("This is usually an exception within an exception.  The trap\n");
 		db_printf("frame shadow registers you are about to see are invalid.\n");
-		db_printf("(read totaly useless)  But R1 to R31 might be interesting.\n");
+		db_printf("(read totally useless)  But R1 to R31 might be interesting.\n");
 		break;
 	}
 	regdump((struct trapframe*)frame);