diff options
author | Matt LaPlante <kernel1@cyberdogtech.com> | 2007-10-19 19:34:40 -0400 |
---|---|---|
committer | Adrian Bunk <bunk@kernel.org> | 2007-10-19 19:34:40 -0400 |
commit | 01dd2fbf0da4019c380b6ca22a074538fb31db5a (patch) | |
tree | 210291bd341c4450c8c51d8db890af0978f4035d /Documentation/powerpc | |
parent | 0f035b8e8491f4ff87f6eec3e3f754d36b39d7a2 (diff) |
typo fixes
Most of these fixes were already submitted for old kernel versions, and were
approved, but for some reason they never made it into the releases.
Because this is a consolidation of a couple old missed patches, it touches both
Kconfigs and documentation texts.
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Adrian Bunk <bunk@kernel.org>
Diffstat (limited to 'Documentation/powerpc')
-rw-r--r-- | Documentation/powerpc/eeh-pci-error-recovery.txt | 4 | ||||
-rw-r--r-- | Documentation/powerpc/mpc52xx-device-tree-bindings.txt | 12 |
2 files changed, 8 insertions, 8 deletions
diff --git a/Documentation/powerpc/eeh-pci-error-recovery.txt b/Documentation/powerpc/eeh-pci-error-recovery.txt index 4530d1bf0286..df7afe43d462 100644 --- a/Documentation/powerpc/eeh-pci-error-recovery.txt +++ b/Documentation/powerpc/eeh-pci-error-recovery.txt | |||
@@ -36,8 +36,8 @@ Causes of EEH Errors | |||
36 | EEH was originally designed to guard against hardware failure, such | 36 | EEH was originally designed to guard against hardware failure, such |
37 | as PCI cards dying from heat, humidity, dust, vibration and bad | 37 | as PCI cards dying from heat, humidity, dust, vibration and bad |
38 | electrical connections. The vast majority of EEH errors seen in | 38 | electrical connections. The vast majority of EEH errors seen in |
39 | "real life" are due to eithr poorly seated PCI cards, or, | 39 | "real life" are due to either poorly seated PCI cards, or, |
40 | unfortunately quite commonly, due device driver bugs, device firmware | 40 | unfortunately quite commonly, due to device driver bugs, device firmware |
41 | bugs, and sometimes PCI card hardware bugs. | 41 | bugs, and sometimes PCI card hardware bugs. |
42 | 42 | ||
43 | The most common software bug, is one that causes the device to | 43 | The most common software bug, is one that causes the device to |
diff --git a/Documentation/powerpc/mpc52xx-device-tree-bindings.txt b/Documentation/powerpc/mpc52xx-device-tree-bindings.txt index e59fcbbe338c..5f7d536cb0c6 100644 --- a/Documentation/powerpc/mpc52xx-device-tree-bindings.txt +++ b/Documentation/powerpc/mpc52xx-device-tree-bindings.txt | |||
@@ -17,12 +17,12 @@ passed by the boot loader to the kernel at boot time. The device tree | |||
17 | describes what devices are present on the board and how they are | 17 | describes what devices are present on the board and how they are |
18 | connected. The device tree can either be passed as a binary blob (as | 18 | connected. The device tree can either be passed as a binary blob (as |
19 | described in Documentation/powerpc/booting-without-of.txt), or passed | 19 | described in Documentation/powerpc/booting-without-of.txt), or passed |
20 | by Open Firmare (IEEE 1275) compatible firmware using an OF compatible | 20 | by Open Firmware (IEEE 1275) compatible firmware using an OF compatible |
21 | client interface API. | 21 | client interface API. |
22 | 22 | ||
23 | This document specifies the requirements on the device-tree for mpc5200 | 23 | This document specifies the requirements on the device-tree for mpc5200 |
24 | based boards. These requirements are above and beyond the details | 24 | based boards. These requirements are above and beyond the details |
25 | specified in either the OpenFirmware spec or booting-without-of.txt | 25 | specified in either the Open Firmware spec or booting-without-of.txt |
26 | 26 | ||
27 | All new mpc5200-based boards are expected to match this document. In | 27 | All new mpc5200-based boards are expected to match this document. In |
28 | cases where this document is not sufficient to support a new board port, | 28 | cases where this document is not sufficient to support a new board port, |
@@ -73,8 +73,8 @@ match on the compatible list; the 'most compatible' driver should be | |||
73 | selected. | 73 | selected. |
74 | 74 | ||
75 | The split between the MPC5200 and the MPC5200B leaves a bit of a | 75 | The split between the MPC5200 and the MPC5200B leaves a bit of a |
76 | connundrum. How should the compatible property be set up to provide | 76 | conundrum. How should the compatible property be set up to provide |
77 | maximum compatability information; but still acurately describe the | 77 | maximum compatibility information; but still accurately describe the |
78 | chip? For the MPC5200; the answer is easy. Most of the SoC devices | 78 | chip? For the MPC5200; the answer is easy. Most of the SoC devices |
79 | originally appeared on the MPC5200. Since they didn't exist anywhere | 79 | originally appeared on the MPC5200. Since they didn't exist anywhere |
80 | else; the 5200 compatible properties will contain only one item; | 80 | else; the 5200 compatible properties will contain only one item; |
@@ -84,7 +84,7 @@ The 5200B is almost the same as the 5200, but not quite. It fixes | |||
84 | silicon bugs and it adds a small number of enhancements. Most of the | 84 | silicon bugs and it adds a small number of enhancements. Most of the |
85 | devices either provide exactly the same interface as on the 5200. A few | 85 | devices either provide exactly the same interface as on the 5200. A few |
86 | devices have extra functions but still have a backwards compatible mode. | 86 | devices have extra functions but still have a backwards compatible mode. |
87 | To express this infomation as completely as possible, 5200B device trees | 87 | To express this information as completely as possible, 5200B device trees |
88 | should have two items in the compatible list; | 88 | should have two items in the compatible list; |
89 | "mpc5200b-<device>\0mpc5200-<device>". It is *strongly* recommended | 89 | "mpc5200b-<device>\0mpc5200-<device>". It is *strongly* recommended |
90 | that 5200B device trees follow this convention (instead of only listing | 90 | that 5200B device trees follow this convention (instead of only listing |
@@ -199,7 +199,7 @@ ethernet@<addr> network mpc5200-fec MPC5200 ethernet device | |||
199 | ata@<addr> ata mpc5200-ata IDE ATA interface | 199 | ata@<addr> ata mpc5200-ata IDE ATA interface |
200 | i2c@<addr> i2c mpc5200-i2c I2C controller | 200 | i2c@<addr> i2c mpc5200-i2c I2C controller |
201 | usb@<addr> usb-ohci-be mpc5200-ohci,ohci-be USB controller | 201 | usb@<addr> usb-ohci-be mpc5200-ohci,ohci-be USB controller |
202 | xlb@<addr> xlb mpc5200-xlb XLB arbritrator | 202 | xlb@<addr> xlb mpc5200-xlb XLB arbitrator |
203 | 203 | ||
204 | Important child node properties | 204 | Important child node properties |
205 | name type description | 205 | name type description |