Lines Matching +full:usb +full:- +full:a +full:- +full:connector
2 xpad - Linux USB driver for Xbox compatible controllers
5 This driver exposes all first-party and third-party Xbox compatible
6 controllers. It has a long history and has enjoyed considerable usage
25 - if you are using a known controller
26 - if you are using a known dance pad
27 - if using an unknown device (one not listed below), what you set in the
28 module configuration for "Map D-PAD to buttons rather than axes for unknown
33 If you said Y it will map the d-pad to buttons, which is needed for dance
36 dpad_to_buttons has no effect for known pads. A erroneous commit message
43 ------------------
45 With a normal controller, the directional pad is mapped to its own X/Y axes.
46 The jstest-program from joystick-1.2.15 (jstest-version 2.1.0) will report 8
49 All 8 axes work, though they all have the same range (-32768..32767)
50 and the zero-setting is not correct for the triggers (I don't know if that
52 didn't have a look at jstest itself yet).
55 right side (A, B, X, Y, black, white) are said to be "analog" and
60 play first person shooters with a pad. Your mileage may vary.
64 ---------------
66 When using a known dance pad, jstest will report 6 axes and 14 buttons.
69 have been made. The old driver would map the d-pad to axes, resulting
73 Known dance pads automatically map the d-pad to buttons and will work
77 of buttons, see section 0.3 - Unknown Controllers
83 -------------------
92 USB adapters
95 All generations of Xbox controllers speak USB over the wire.
97 - Original Xbox controllers use a proprietary connector and require adapters.
98 - Wireless Xbox 360 controllers require a 'Xbox 360 Wireless Gaming Receiver
100 - Wired Xbox 360 controllers use standard USB connectors.
101 - Xbox One controllers can be wireless but speak Wi-Fi Direct and are not
103 - Xbox One controllers can be wired and use standard Micro-USB connectors.
107 Original Xbox USB adapters
108 --------------------------
111 adapter cable to break out the proprietary connector's pins to USB.
114 Such a cable is pretty easy to build. The Controller itself is a USB
115 compound device (a hub with three ports for two expansion slots and
116 the controller device) with the only difference in a nonstandard connector
117 (5 pins vs. 4 on standard USB 1.0 connectors).
119 You just need to solder a USB connector onto the cable and keep the
126 you can still use the controller with your X-Box, if you have one ;)
135 /sys/kernel/debug/usb/devices. There should be an entry like those:
137 .. code-block:: none
142 P: Vendor=05fd ProdID=107a Rev= 1.00
148 .. code-block:: none
164 For a full list of supported controllers and associated vendor and product
167 As of the historic version 0.0.6 (2006-10-10) the following devices
180 If you have an unrecognized controller please see 0.3 - Unknown Controllers
194 If you're using a normal controller, there should be a single line showing
196 the sticks and push the buttons. If you're using a dance pad, it should
207 http://euc.jp/periphs/xbox-controller.ja.html.
209 His useful info and both the usb-skeleton as well as the iforce input driver
210 (Greg Kroah-Hartmann; Vojtech Pavlik) helped a lot in rapid prototyping
218 .. [1] http://euc.jp/periphs/xbox-controller.ja.html (ITO Takayuki)
219 .. [2] http://xpad.xbox-scene.com/
227 2002-07-16 - Marko Friedemann <mfr@bmx-chemnitz.de>
228 - original doc
230 2005-03-19 - Dominic Cerquetti <binary1230@yahoo.com>
231 - added stuff for dance pads, new d-pad->axes mappings
234 'git log --follow Documentation/input/devices/xpad.rst'