Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The wrong product ID is exposed for the Wireless 360 controllers #54

Closed
Omar007 opened this issue Nov 23, 2016 · 5 comments
Closed

The wrong product ID is exposed for the Wireless 360 controllers #54

Omar007 opened this issue Nov 23, 2016 · 5 comments

Comments

@Omar007
Copy link

Omar007 commented Nov 23, 2016 •
edited
Loading

The current implementation exposes the wireless receiver itself as 4 controllers, however the receiver and controllers are actually different devices with their own product ID.

The receiver has a product ID of 0x0719 and is a hub-style device that has 4 controllers attached to it.
The controllers have a different product ID; 0x02A1.

Right now you get 4 controllers with a product ID of 0x0719.
Instead, the receiver should be an unique device with 4 children; receiver (0x0719) -> 4 controllers (0x02A1).

Because the wrong PID is advertised by the drivers, some games do not automatically pick up the controller as an Xbox controller.
This was discovered through a game running in WINE [1].

NOTE1: This potentially also applies to the Xbox receiver (PID 0x0291) but I can't personally verify this.
NOTE2: Bug was originally reported (by me) on the kernel.org bugzilla [2] but received no response for 3 months.
paroj added a commit that referenced this issue Nov 24, 2016
@paroj
Input: xpad - expose correct id for the Wireless 360 controllers
80f4fcd 
see #54
@paroj
Copy link
Owner

paroj commented Nov 24, 2016

does the above commit help? (x360w_id branch)

@cgutman
Copy link
Contributor

cgutman commented Nov 25, 2016

FWIW, Windows also exposes wireless Xbox 360 controllers with product ID 0x02A1.

@paroj
Copy link
Owner

paroj commented Nov 25, 2016

yeah, from the Wine Bugreport:

Windows:
TL/DR; Both the receiver and controllers are unique devices.

  • Receiver
    -- Separate device, attached to a USB port, hub-style device ('Xbox 360 peripheral')
    -- Product ID 0x0719
  • Controllers (x4)
    -- Separate device, attached to the receiver, game controller
    -- Product ID 0x02A1

Linux:
TL/DR; The receiver and controllers are the same device (receiver = 4 controllers).

  • Receiver
    -- Attached to a USB port, seen as 4 game controllers.
    -- Product ID 0x0719.
  • Controller (4x)
    -- Not handled as a separate device.
    -- Should have Product ID = 0x02A1.
    -- In the system tree the controllers are located underneath the receiver:
    /sys/bus/usb/devices/[receiver usb]/[receiver-usb]:[controller]

@Omar007
Copy link
Author

Omar007 commented Nov 26, 2016 •
edited
Loading

It does indeed help :)
If there are wireless controllers with an ID other than 0x02A1 this might have to be revised at a later time to account for that, but for now this seems to do it just fine.

paroj added a commit that referenced this issue Dec 27, 2016
@paroj
Input: xpad - use correct product id for x360w controllers
b97dc59 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see #54
paroj added a commit that referenced this issue Dec 27, 2016
@paroj
Input: xpad - use correct product id for x360w controllers
89c05c2 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see #54
@cgutman
Copy link
Contributor

cgutman commented Dec 30, 2016

This patch is queued for upstream so this issue can probably be closed now.

@paroj paroj closed this as completed Dec 30, 2016
cgutman pushed a commit to cgutman/xpad that referenced this issue Jan 3, 2017
@paroj @cgutman
Input: xpad - use correct product id for x360w controllers
953291a 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
cgutman pushed a commit to cgutman/xpad that referenced this issue Jan 3, 2017
@paroj @cgutman
Input: xpad - use correct product id for x360w controllers
f098f5f 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
sudipm-mukherjee pushed a commit to sudipm-mukherjee/parport that referenced this issue Jan 3, 2017
@paroj @dtor
Input: xpad - use correct product id for x360w controllers
b6fc513 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
jollaman999 pushed a commit to jollaman999/jolla-kernel_bullhead that referenced this issue Jan 14, 2017
@paroj @jollaman999
Input: xpad - use correct product id for x360w controllers
f30f658 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
jollaman999 pushed a commit to jollaman999/jolla-kernel_bullhead that referenced this issue Jan 14, 2017
@paroj @jollaman999
Input: xpad - use correct product id for x360w controllers
36cd7fc 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
jollaman999 pushed a commit to jollaman999/jolla-kernel_bullhead that referenced this issue Jan 14, 2017
@paroj @jollaman999
Input: xpad - use correct product id for x360w controllers
84837b2 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Whissi pushed a commit to Whissi/linux-stable that referenced this issue Jan 20, 2017
@paroj @gregkh
Input: xpad - use correct product id for x360w controllers
5137779 
commit b6fc513 upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Whissi pushed a commit to Whissi/linux-stable that referenced this issue Jan 20, 2017
@paroj @gregkh
Input: xpad - use correct product id for x360w controllers
5975358 
commit b6fc513 upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
dsd pushed a commit to endlessm/linux that referenced this issue Jan 27, 2017
@paroj @rtg-canonical
Input: xpad - use correct product id for x360w controllers
1eff0da 
BugLink: http://bugs.launchpad.net/bugs/1658099

commit b6fc513 upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
bgly pushed a commit to powervm/ibmvscsis that referenced this issue Jan 31, 2017
@paroj
Input: xpad - use correct product id for x360w controllers
01ee317 
BugLink: http://bugs.launchpad.net/bugs/1658091

commit b6fc513 upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
Signed-off-by: Luis Henriques <luis.henriques@canonical.com>
Whissi pushed a commit to Whissi/linux-stable that referenced this issue Feb 1, 2017
@paroj
Input: xpad - use correct product id for x360w controllers
242f317 
commit b6fc513 upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
rachanta pushed a commit to rachanta/racer-n5x that referenced this issue Feb 3, 2017
@paroj @rachanta
Input: xpad - use correct product id for x360w controllers
c2712cb 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
rachanta pushed a commit to rachanta/racer-n5x that referenced this issue Feb 4, 2017
@paroj @rachanta
Input: xpad - use correct product id for x360w controllers
f257d34 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
rachanta pushed a commit to rachanta/racer-n5x that referenced this issue Feb 5, 2017
@paroj @rachanta
Input: xpad - use correct product id for x360w controllers
79e30cc 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
evan-a-a pushed a commit to evan-a-a/linux-braswell that referenced this issue Feb 6, 2017
@paroj @evan-a-a
Input: xpad - use correct product id for x360w controllers
83cb64e 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
rachanta pushed a commit to rachanta/racer-n5x that referenced this issue Feb 7, 2017
@paroj @rachanta
Input: xpad - use correct product id for x360w controllers
0d61558 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
rachanta pushed a commit to rachanta/racer-n5x that referenced this issue Feb 7, 2017
@paroj @rachanta
Input: xpad - use correct product id for x360w controllers
998fea4 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
rachanta pushed a commit to rachanta/racer-n5x that referenced this issue Feb 8, 2017
@paroj @rachanta
Input: xpad - use correct product id for x360w controllers
de2cec3 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
rachanta pushed a commit to rachanta/racer-n5x that referenced this issue Feb 9, 2017
@paroj @rachanta
Input: xpad - use correct product id for x360w controllers
806e123 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
rachanta pushed a commit to rachanta/racer-n5x that referenced this issue Feb 10, 2017
@paroj @rachanta
Input: xpad - use correct product id for x360w controllers
4b34a65 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
rachanta pushed a commit to rachanta/racer-n5x that referenced this issue Feb 13, 2017
@paroj @rachanta
Input: xpad - use correct product id for x360w controllers
c56f29b 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
sabarop pushed a commit to sabarop/kernel_sony_msm8994 that referenced this issue Sep 16, 2021
@paroj @sabarop
Input: xpad - use correct product id for x360w controllers
5f9c661 
currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Andrey Cherepkov <andreiskull@gmail.com>
sabarop pushed a commit to sabarop/kernel_sony_msm8994 that referenced this issue Sep 21, 2021
@paroj @sabarop
Input: xpad - use correct product id for x360w controllers
1bb4863 
commit b6fc513 upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
sabarop pushed a commit to sabarop/kernel_sony_msm8994 that referenced this issue Sep 23, 2021
@paroj @sabarop
Input: xpad - use correct product id for x360w controllers
a39ead8 
commit b6fc513 upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
AShiningRay pushed a commit to AShiningRay/SwanKernel-LGV20_G5_G6 that referenced this issue Oct 27, 2021
@paroj @AShiningRay
Input: xpad - use correct product id for x360w controllers
b417212 
[ Upstream commit b6fc513 ]

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
AShiningRay pushed a commit to AShiningRay/SwanKernel-LGV20_G5_G6 that referenced this issue Oct 28, 2021
@paroj @AShiningRay
Input: xpad - use correct product id for x360w controllers
dd68136 
[ Upstream commit b6fc513 ]

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
unkl933 pushed a commit to unkl933/kernel_xiaomi_msm8996-3.18 that referenced this issue Oct 31, 2021
@paroj @unkl933
Input: xpad - use correct product id for x360w controllers
14a2a8f 
[ Upstream commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d ]

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
turex pushed a commit to turex/labyrinth_kernel_prague that referenced this issue Nov 30, 2021
@paroj @turex
Input: xpad - use correct product id for x360w controllers
2bb5645 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
althafvly pushed a commit to MOTO-M8916/android_kernel_motorola_msm8916 that referenced this issue Dec 14, 2021
@paroj @althafvly
Input: xpad - use correct product id for x360w controllers
72c78a7 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
DeepakChaurasia30 pushed a commit to DeepakChaurasia30/kernel_oppo_msm8916-offical that referenced this issue Jan 11, 2022
@paroj @DeepakChaurasia30
Input: xpad - use correct product id for x360w controllers
f4c4fa2 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
goldfish07 pushed a commit to goldfish07/android_kernel_samsung_j8y18lte that referenced this issue Feb 6, 2022
@paroj @goldfish07
Input: xpad - use correct product id for x360w controllers
2c1419d 
[ Upstream commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d ]

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
log1cs pushed a commit to LycorisOSS/android_kernel_nokia_msm8937 that referenced this issue Mar 30, 2022
@paroj @log1cs
Input: xpad - use correct product id for x360w controllers
0175607 
[ Upstream commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d ]

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
ggow pushed a commit to lineage16-suez/kernel_amazon_suez that referenced this issue Apr 11, 2022
@paroj @ggow
Input: xpad - use correct product id for x360w controllers
9e9f3e2 
[ Upstream commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d ]

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
(cherry picked from commit e02c9723ccdda0cc73c1acf21d140e7a67578f15)
thenextgod pushed a commit to thenextgod/kernel_msm8976 that referenced this issue Jul 6, 2022
@paroj @thenextgod
Input: xpad - use correct product id for x360w controllers
cfd7d18 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
fakemanoan pushed a commit to fakemanoan/android_kernel_samsung_universal7420 that referenced this issue Sep 24, 2022
@paroj @fakemanoan
Input: xpad - use correct product id for x360w controllers
86e7b2c 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
MdHusainhfz pushed a commit to MdHusainhfz/android_kernel_samsung_a6plte that referenced this issue Jan 4, 2023
@paroj @MdHusainhfz
Input: xpad - use correct product id for x360w controllers
0d61c5c 
[ Upstream commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d ]

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
unkl933 pushed a commit to unkl933/kernel_xiaomi_msm8996-3.18 that referenced this issue Jan 9, 2023
@paroj @unkl933
Input: xpad - use correct product id for x360w controllers
a683346 
[ Upstream commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d ]

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
andrew2193 pushed a commit to andrew2193/Pryo that referenced this issue Jun 17, 2023
@paroj @andrew2193
Input: xpad - use correct product id for x360w controllers
6d2e3f6 
[ Upstream commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d ]

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
prototype74 pushed a commit to prototype74/android_kernel_samsung_msm8916 that referenced this issue Dec 21, 2023
@paroj @prototype74
Input: xpad - use correct product id for x360w controllers
337f24e 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
bluess57 pushed a commit to bluess57/android_kernel_samsung_universal5433 that referenced this issue Jan 10, 2024
@paroj
Input: xpad - use correct product id for x360w controllers
20b13d5 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
bluess57 pushed a commit to bluess57/android_kernel_samsung_universal5433 that referenced this issue Jan 11, 2024
@paroj
Input: xpad - use correct product id for x360w controllers
26c5842 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
metterschlg pushed a commit to metterschlg/android_kernel_samsung_universal5433 that referenced this issue Jan 21, 2024
@paroj @metterschlg
Input: xpad - use correct product id for x360w controllers
c365d12 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
schwienernitzel pushed a commit to schwienernitzel/android_kernel_huawei_mozart-old that referenced this issue Jun 17, 2024
@paroj @schwienernitzel
Input: xpad - use correct product id for x360w controllers
f5194bb 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
schwienernitzel pushed a commit to schwienernitzel/android_kernel_huawei_mozart-old that referenced this issue Jun 17, 2024
@paroj @schwienernitzel
Input: xpad - use correct product id for x360w controllers
17a1b15 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
schwienernitzel pushed a commit to schwienernitzel/android_kernel_huawei_mozart-old that referenced this issue Jun 26, 2024
@paroj @schwienernitzel
Input: xpad - use correct product id for x360w controllers
30e0389 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
NotNoelChannel pushed a commit to NotNoelChannel/android_kernel_huawei_msm8909 that referenced this issue Sep 27, 2024
@paroj @NotNoelChannel
Input: xpad - use correct product id for x360w controllers
e0a34a0 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
NotNoelChannel pushed a commit to NotNoelChannel/android_kernel_huawei_msm8909 that referenced this issue Sep 28, 2024
@paroj @NotNoelChannel
Input: xpad - use correct product id for x360w controllers
b0194d2 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
NotNoelChannel pushed a commit to NotNoelChannel/android_kernel_huawei_msm8909 that referenced this issue Sep 29, 2024
@paroj @NotNoelChannel
Input: xpad - use correct product id for x360w controllers
85771c9 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
NotNoelChannel pushed a commit to NotNoelChannel/android_kernel_huawei_msm8909 that referenced this issue Sep 29, 2024
@paroj @NotNoelChannel
Input: xpad - use correct product id for x360w controllers
27288b7 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
RebelLion420 pushed a commit to RebelLion420/RebelKernel_perry that referenced this issue Oct 24, 2024
@paroj @RebelLion420
Input: xpad - use correct product id for x360w controllers
8efda5f 
[ Upstream commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d ]

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
NotNoelChannel pushed a commit to NotNoelChannel/android_kernel_samsung_kiran that referenced this issue Mar 25, 2025
@paroj @NotNoelChannel
Input: xpad - use correct product id for x360w controllers
cca815c 
commit b6fc513da50c5dbc457a8ad6b58b046a6a68fd9d upstream.

currently the controllers get the same product id as the wireless
receiver. However the controllers actually have their own product id.

The patch makes the driver expose the same product id as the windows
driver.

This improves compatibility when running applications with WINE.

see paroj/xpad#54

Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cgutman @paroj @Omar007