Module Name: src
Committed By: andvar
Date: Fri Sep 8 19:04:29 UTC 2023
Modified Files:
src/sys/arch/hp300/DOC: Debug.tips TODO.hp300
Log Message:
fix few typos in the text of Debug.tips and TODO.hp300 docs.
To generate a diff of this commit:
cvs rdiff -u -r1.5 -r1.6 src/sys/arch/hp300/DOC/Debug.tips
cvs rdiff -u -r1.3 -r1.4 src/sys/arch/hp300/DOC/TODO.hp300
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: src/sys/arch/hp300/DOC/Debug.tips
diff -u src/sys/arch/hp300/DOC/Debug.tips:1.5 src/sys/arch/hp300/DOC/Debug.tips:1.6
--- src/sys/arch/hp300/DOC/Debug.tips:1.5 Sun Dec 11 12:17:13 2005
+++ src/sys/arch/hp300/DOC/Debug.tips Fri Sep 8 19:04:28 2023
@@ -1,4 +1,4 @@
-$NetBSD: Debug.tips,v 1.5 2005/12/11 12:17:13 christos Exp $
+$NetBSD: Debug.tips,v 1.6 2023/09/08 19:04:28 andvar Exp $
NOTE: this description applies to the hp300 system with the old BSD
virtual memory system. It has not been updated to reflect the new,
@@ -13,9 +13,9 @@ Some quick notes on the HPBSD VM layout
Physical memory:
Physical memory always ends at the top of the 32 bit address space; i.e. the
-last addressible byte is at 0xFFFFFFFF. Hence, the start of physical memory
+last addressable byte is at 0xFFFFFFFF. Hence, the start of physical memory
varies depending on how much memory is installed. The kernel variable "lowram"
-contains the starting locatation of memory as provided by the ROM.
+contains the starting location of memory as provided by the ROM.
The low 128k (I think) of the physical address space is occupied by the ROM.
This is accessible via /dev/mem *only* if the kernel is compiled with DEBUG.
@@ -157,7 +157,7 @@ the user page table. Look at the last 2
was intended to be a read-only page to protect the user structure from the
kernel stack. Currently it is read/write and actually allocated. Hence
it can wind up being a second page for the kernel stack. The third is the
-kernel stack. The last 253 should be zero. Hence, indirecing through the
+kernel stack. The last 253 should be zero. Hence, indirecting through the
third of these last 256 PTEs will give you the kernel stack page.
An alternate way to do this is to use the p_addr field of the proc structure
@@ -172,7 +172,7 @@ useful information. This dates back to
exception handling code and had no kernel adb or even kernel crash dump code.
"trap type" (decimal) is as defined in hp300/trap.h, it doesn't really
correlate with anything useful. "code" (hex) is only useful for MMU
-(trap type 8) errors. It is the concatination of the MMU status register
+(trap type 8) errors. It is the concatenation of the MMU status register
(see hp300/cpu.h) in the high 16 bits and the 68020 special status word
(see the 020 manual page 6-17) in the low 16. "v" (hex) is the virtual
address which caused the fault. "pid" (decimal) is the ID of the process
Index: src/sys/arch/hp300/DOC/TODO.hp300
diff -u src/sys/arch/hp300/DOC/TODO.hp300:1.3 src/sys/arch/hp300/DOC/TODO.hp300:1.4
--- src/sys/arch/hp300/DOC/TODO.hp300:1.3 Tue Apr 12 21:05:37 2022
+++ src/sys/arch/hp300/DOC/TODO.hp300 Fri Sep 8 19:04:28 2023
@@ -1,4 +1,4 @@
-$NetBSD: TODO.hp300,v 1.3 2022/04/12 21:05:37 andvar Exp $
+$NetBSD: TODO.hp300,v 1.4 2023/09/08 19:04:28 andvar Exp $
1. Create and use an interrupt stack.
Well actually, use the master SP for kernel stacks instead of
@@ -15,7 +15,7 @@ $NetBSD: TODO.hp300,v 1.3 2022/04/12 21:
however.
3. Sendsig/sigreturn are pretty bogus.
- Currently we can call a signal handler even if an excpetion
+ Currently we can call a signal handler even if an exception
occurs in the middle of an instruction. This causes the handler
to return right back to the middle of the offending instruction
which will most likely lead to another exception/signal.
@@ -43,7 +43,7 @@ $NetBSD: TODO.hp300,v 1.3 2022/04/12 21:
it does eat up a significant piece of kernel address space.
6. Create a 32-bit timer.
- Timers 2 and 3 on the MC6840 clock chip can be concatonated together to
+ Timers 2 and 3 on the MC6840 clock chip can be concatenated together to
get a 32-bit countdown timer. There are at least three uses for this:
1. Monitoring the interval timer ("clock") to detect lost "ticks".
(Idea from Scott Marovich)
