summaryrefslogtreecommitdiffstats
path: root/Documentation/powerpc/SBC8260_memory_mapping.txt
diff options
context:
space:
mode:
authorRalf Baechle <ralf@linux-mips.org>2000-08-08 12:37:17 +0000
committerRalf Baechle <ralf@linux-mips.org>2000-08-08 12:37:17 +0000
commit9aa9eb41942b918f385ccabd2efdd6e7e4232165 (patch)
tree20bec7da036d31ec185dfc1dcc00753c7ac9b170 /Documentation/powerpc/SBC8260_memory_mapping.txt
parent87075e049581f880f01eb0b41aa6ac807b299e35 (diff)
Merge with Linux 2.4.0-test6-pre1.
Diffstat (limited to 'Documentation/powerpc/SBC8260_memory_mapping.txt')
-rw-r--r--Documentation/powerpc/SBC8260_memory_mapping.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/powerpc/SBC8260_memory_mapping.txt b/Documentation/powerpc/SBC8260_memory_mapping.txt
index c61827c07..e6e9ee050 100644
--- a/Documentation/powerpc/SBC8260_memory_mapping.txt
+++ b/Documentation/powerpc/SBC8260_memory_mapping.txt
@@ -125,7 +125,7 @@ if you have questions, comments or corrections.
Although platform dependent, and certainly the case for embedded
8xx, traditionally memory is mapped at physical address zero,
- and I/O devices above phsical address 0x80000000. The lowest
+ and I/O devices above physical address 0x80000000. The lowest
and highest (above 0xf0000000) I/O addresses are traditionally
used for devices or registers we need to map during kernel
initialization and prior to KVM operation. For this reason,