From: Vicki Pfau <vi@endrift.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Cc: Sam Lantinga <slouken@libsdl.org>,
Pavel Rojtberg <rojtberg@gmail.com>, Vicki Pfau <vi@endrift.com>
Subject: [PATCH 2/2] Input: xpad - Add GameSir VID for Xbox One controllers
Date: Tue, 6 Jun 2023 18:28:12 -0700 [thread overview]
Message-ID: <20230607012812.379640-3-vi@endrift.com> (raw)
In-Reply-To: <20230607012812.379640-1-vi@endrift.com>
From: Sam Lantinga <slouken@libsdl.org>
Signed-off-by: Sam Lantinga <slouken@libsdl.org>
Signed-off-by: Vicki Pfau <vi@endrift.com>
---
drivers/input/joystick/xpad.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.c
index 745047215e42..459b5c507399 100644
--- a/drivers/input/joystick/xpad.c
+++ b/drivers/input/joystick/xpad.c
@@ -499,6 +499,7 @@ static const struct usb_device_id xpad_table[] = {
XPAD_XBOXONE_VENDOR(0x2dc8), /* 8BitDo Pro 2 Wired Controller for Xbox */
XPAD_XBOXONE_VENDOR(0x2e24), /* Hyperkin Duke Xbox One pad */
XPAD_XBOX360_VENDOR(0x2f24), /* GameSir controllers */
+ XPAD_XBOXONE_VENDOR(0x3537), /* GameSir Controllers */
XPAD_XBOX360_VENDOR(0x31e3), /* Wooting Keyboards */
XPAD_XBOX360_VENDOR(0x3285), /* Nacon GC-100 */
{ }
--
2.40.1
next prev parent reply other threads:[~2023-06-07 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 1:28 [PATCH 0/2] Input: xpad - Additional controller support Vicki Pfau
2023-06-07 1:28 ` [PATCH 1/2] Input: xpad - fix support for some third-party controllers Vicki Pfau
2023-07-07 23:59 ` Dmitry Torokhov
2023-06-07 1:28 ` Vicki Pfau [this message]
2023-07-08 0:00 ` [PATCH 2/2] Input: xpad - Add GameSir VID for Xbox One controllers Dmitry Torokhov
2023-07-01 2:38 ` [PATCH 0/2] Input: xpad - Additional controller support Vicki Pfau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230607012812.379640-3-vi@endrift.com \
--to=vi@endrift.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=rojtberg@gmail.com \
--cc=slouken@libsdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).