diff options
author | Matt LaPlante <kernel1@cyberdogtech.com> | 2007-05-09 01:35:06 -0400 |
---|---|---|
committer | Adrian Bunk <bunk@stusta.de> | 2007-05-09 02:58:15 -0400 |
commit | a982ac06b069f6ee9ea1b64f4ce68cdf2e138742 (patch) | |
tree | fb120a416db15d09722e8780b7a09d0da1a9b94e /Documentation/input | |
parent | 148e423f909e14564d8af13239c5d060f7df273e (diff) |
misc doc and kconfig typos
Fix various typos in kernel docs and Kconfigs, 2.6.21-rc4.
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/input')
-rw-r--r-- | Documentation/input/atarikbd.txt | 4 | ||||
-rw-r--r-- | Documentation/input/xpad.txt | 6 |
2 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/input/atarikbd.txt b/Documentation/input/atarikbd.txt index 668f4d0d97d..ab050621e20 100644 --- a/Documentation/input/atarikbd.txt +++ b/Documentation/input/atarikbd.txt | |||
@@ -179,9 +179,9 @@ reporting mode for joystick 1, with both buttons being logically assigned to | |||
179 | the mouse. After any joystick command, the ikbd assumes that joysticks are | 179 | the mouse. After any joystick command, the ikbd assumes that joysticks are |
180 | connected to both Joystick0 and Joystick1. Any mouse command (except MOUSE | 180 | connected to both Joystick0 and Joystick1. Any mouse command (except MOUSE |
181 | DISABLE) then causes port 0 to again be scanned as if it were a mouse, and | 181 | DISABLE) then causes port 0 to again be scanned as if it were a mouse, and |
182 | both buttons are logically connected to it. If a mouse diable command is | 182 | both buttons are logically connected to it. If a mouse disable command is |
183 | received while port 0 is presumed to be a mouse, the button is logically | 183 | received while port 0 is presumed to be a mouse, the button is logically |
184 | assigned to Joystick1 ( until the mouse is reenabled by another mouse command). | 184 | assigned to Joystick1 (until the mouse is reenabled by another mouse command). |
185 | 185 | ||
186 | 9. ikbd Command Set | 186 | 9. ikbd Command Set |
187 | 187 | ||
diff --git a/Documentation/input/xpad.txt b/Documentation/input/xpad.txt index 5427bdf225e..aae0d404c56 100644 --- a/Documentation/input/xpad.txt +++ b/Documentation/input/xpad.txt | |||
@@ -65,15 +65,15 @@ of buttons, see section 0.3 - Unknown Controllers | |||
65 | I've tested this with Stepmania, and it works quite well. | 65 | I've tested this with Stepmania, and it works quite well. |
66 | 66 | ||
67 | 67 | ||
68 | 0.3 Unkown Controllers | 68 | 0.3 Unknown Controllers |
69 | ---------------------- | 69 | ---------------------- |
70 | If you have an unkown xbox controller, it should work just fine with | 70 | If you have an unknown xbox controller, it should work just fine with |
71 | the default settings. | 71 | the default settings. |
72 | 72 | ||
73 | HOWEVER if you have an unknown dance pad not listed below, it will not | 73 | HOWEVER if you have an unknown dance pad not listed below, it will not |
74 | work UNLESS you set "dpad_to_buttons" to 1 in the module configuration. | 74 | work UNLESS you set "dpad_to_buttons" to 1 in the module configuration. |
75 | 75 | ||
76 | PLEASE if you have an unkown controller, email Dom <binary1230@yahoo.com> with | 76 | PLEASE, if you have an unknown controller, email Dom <binary1230@yahoo.com> with |
77 | a dump from /proc/bus/usb and a description of the pad (manufacturer, country, | 77 | a dump from /proc/bus/usb and a description of the pad (manufacturer, country, |
78 | whether it is a dance pad or normal controller) so that we can add your pad | 78 | whether it is a dance pad or normal controller) so that we can add your pad |
79 | to the list of supported devices, ensuring that it will work out of the | 79 | to the list of supported devices, ensuring that it will work out of the |