Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

Input: joystick - refer to /dev/input/js0 in documentation

Nowadays the joystick device nodes are created under /dev/input, reflect
this in the documentation in order to make copy and paste easier for
users.

Signed-off-by: Antonio Ospite <ospite@studenti.unina.it>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

authored by

Antonio Ospite and committed by
Dmitry Torokhov
7d0e6192 e585c40b

+5 -5
+1 -1
Documentation/input/joystick-api.txt
··· 16 16 17 17 By default, the device is opened in blocking mode. 18 18 19 - int fd = open ("/dev/js0", O_RDONLY); 19 + int fd = open ("/dev/input/js0", O_RDONLY); 20 20 21 21 22 22 2. Event Reading
+4 -4
Documentation/input/joystick.txt
··· 116 116 For testing the joystick driver functionality, there is the jstest 117 117 program in the utilities package. You run it by typing: 118 118 119 - jstest /dev/js0 119 + jstest /dev/input/js0 120 120 121 121 And it should show a line with the joystick values, which update as you 122 122 move the stick, and press its buttons. The axes should all be zero when the ··· 136 136 some analog joysticks, that either do not use linear resistors, or if you 137 137 want better precision, you can use the jscal program 138 138 139 - jscal -c /dev/js0 139 + jscal -c /dev/input/js0 140 140 141 141 included in the joystick package to set better correction coefficients than 142 142 what the driver would choose itself. ··· 145 145 calibration using the jstest command, and if you do, you then can save the 146 146 correction coefficients into a file 147 147 148 - jscal -p /dev/js0 > /etc/joystick.cal 148 + jscal -p /dev/input/js0 > /etc/joystick.cal 149 149 150 150 And add a line to your rc script executing that file 151 151 ··· 556 556 557 557 5. FAQ 558 558 ~~~~~~ 559 - Q: Running 'jstest /dev/js0' results in "File not found" error. What's the 559 + Q: Running 'jstest /dev/input/js0' results in "File not found" error. What's the 560 560 cause? 561 561 A: The device files don't exist. Create them (see section 2.2). 562 562