forked from Minki/linux
1ff5fa3c67
After initially connecting a wired Xbox 360 controller or sending it a command to change LEDs, a status/response packet is interpreted as controller input. This causes the state of buttons represented in byte 2 of the controller data packet to be incorrect until the next valid input packet. Wireless Xbox 360 controllers are not affected. Writing a new value to the LED device while holding the Start button and running jstest is sufficient to reproduce this bug. An event will come through with the Start button released. Xboxdrv also won't attempt to read controller input from a packet where byte 0 is non-zero. It also checks that byte 1 is 0x14, but that value differs between wired and wireless controllers and this code is shared by both. I think just checking byte 0 is enough to eliminate unwanted packets. The following are some examples of 3-byte status packets I saw: 01 03 02 02 03 00 03 03 03 08 03 00 Signed-off-by: Cameron Gutman <aicommander@gmail.com> Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com> Cc: stable@vger.kernel.org Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> |
||
|---|---|---|
| .. | ||
| iforce | ||
| a3d.c | ||
| adi.c | ||
| amijoy.c | ||
| analog.c | ||
| as5011.c | ||
| cobra.c | ||
| db9.c | ||
| gamecon.c | ||
| gf2k.c | ||
| grip_mp.c | ||
| grip.c | ||
| guillemot.c | ||
| interact.c | ||
| joydump.c | ||
| Kconfig | ||
| magellan.c | ||
| Makefile | ||
| maplecontrol.c | ||
| sidewinder.c | ||
| spaceball.c | ||
| spaceorb.c | ||
| stinger.c | ||
| tmdc.c | ||
| turbografx.c | ||
| twidjoy.c | ||
| walkera0701.c | ||
| warrior.c | ||
| xpad.c | ||
| zhenhua.c | ||