diff options
Diffstat (limited to 'Documentation/powerpc')
-rw-r--r-- | Documentation/powerpc/booting-without-of.txt | 4 | ||||
-rw-r--r-- | Documentation/powerpc/eeh-pci-error-recovery.txt | 2 | ||||
-rw-r--r-- | Documentation/powerpc/hvcs.txt | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt index bfcd95dd3c36..042c0cfa94cb 100644 --- a/Documentation/powerpc/booting-without-of.txt +++ b/Documentation/powerpc/booting-without-of.txt | |||
@@ -573,7 +573,7 @@ implementation of Open Firmware or an implementation compatible with | |||
573 | the Open Firmware client interface, those properties will be created | 573 | the Open Firmware client interface, those properties will be created |
574 | by the trampoline code in the kernel's prom_init() file. For example, | 574 | by the trampoline code in the kernel's prom_init() file. For example, |
575 | that's where you'll have to add code to detect your board model and | 575 | that's where you'll have to add code to detect your board model and |
576 | set the platform number. However, when using the flatenned device-tree | 576 | set the platform number. However, when using the flattened device-tree |
577 | entry point, there is no prom_init() pass, and thus you have to | 577 | entry point, there is no prom_init() pass, and thus you have to |
578 | provide those properties yourself. | 578 | provide those properties yourself. |
579 | 579 | ||
@@ -689,7 +689,7 @@ is present). | |||
689 | 4) Note about node and property names and character set | 689 | 4) Note about node and property names and character set |
690 | ------------------------------------------------------- | 690 | ------------------------------------------------------- |
691 | 691 | ||
692 | While open firmware provides more flexibe usage of 8859-1, this | 692 | While open firmware provides more flexible usage of 8859-1, this |
693 | specification enforces more strict rules. Nodes and properties should | 693 | specification enforces more strict rules. Nodes and properties should |
694 | be comprised only of ASCII characters 'a' to 'z', '0' to | 694 | be comprised only of ASCII characters 'a' to 'z', '0' to |
695 | '9', ',', '.', '_', '+', '#', '?', and '-'. Node names additionally | 695 | '9', ',', '.', '_', '+', '#', '?', and '-'. Node names additionally |
diff --git a/Documentation/powerpc/eeh-pci-error-recovery.txt b/Documentation/powerpc/eeh-pci-error-recovery.txt index 3764dd4b12cb..be8867d03db8 100644 --- a/Documentation/powerpc/eeh-pci-error-recovery.txt +++ b/Documentation/powerpc/eeh-pci-error-recovery.txt | |||
@@ -116,7 +116,7 @@ At this time, a generic EEH recovery mechanism has been implemented, | |||
116 | so that individual device drivers do not need to be modified to support | 116 | so that individual device drivers do not need to be modified to support |
117 | EEH recovery. This generic mechanism piggy-backs on the PCI hotplug | 117 | EEH recovery. This generic mechanism piggy-backs on the PCI hotplug |
118 | infrastructure, and percolates events up through the userspace/udev | 118 | infrastructure, and percolates events up through the userspace/udev |
119 | infrastructure. Followiing is a detailed description of how this is | 119 | infrastructure. Following is a detailed description of how this is |
120 | accomplished. | 120 | accomplished. |
121 | 121 | ||
122 | EEH must be enabled in the PHB's very early during the boot process, | 122 | EEH must be enabled in the PHB's very early during the boot process, |
diff --git a/Documentation/powerpc/hvcs.txt b/Documentation/powerpc/hvcs.txt index 1e38166f4e54..f93462c5db25 100644 --- a/Documentation/powerpc/hvcs.txt +++ b/Documentation/powerpc/hvcs.txt | |||
@@ -259,7 +259,7 @@ This index of '2' means that in order to connect to vty-server adapter | |||
259 | 259 | ||
260 | It should be noted that due to the system hotplug I/O capabilities of a | 260 | It should be noted that due to the system hotplug I/O capabilities of a |
261 | system the /dev/hvcs* entry that interacts with a particular vty-server | 261 | system the /dev/hvcs* entry that interacts with a particular vty-server |
262 | adapter is not guarenteed to remain the same across system reboots. Look | 262 | adapter is not guaranteed to remain the same across system reboots. Look |
263 | in the Q & A section for more on this issue. | 263 | in the Q & A section for more on this issue. |
264 | 264 | ||
265 | --------------------------------------------------------------------------- | 265 | --------------------------------------------------------------------------- |