From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 212999] New: xpad map Xbox 360 controller incorrect
Date: Sat, 08 May 2021 23:13:44 +0000 [thread overview]
Message-ID: <bug-212999-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=212999
Bug ID: 212999
Summary: xpad map Xbox 360 controller incorrect
Product: Drivers
Version: 2.5
Kernel Version: 5.12.1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: anton17082003@gmail.com
Regression: No
I have DEXP G-4 XI controller with XInput of Xbox 360 pad
This pad has idVendor 0x045e and idProduct 0x028e
But I don't receive any input events on /dev/input/js0 or /dev/input/event11
until I found this python script
https://gist.github.com/dnmodder/de2df973323b7c6acf45f40dc66e8db3 that fixes it
and it really helped me with it. But I think it must be fixed in xpad driver
without any third party scripts
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-05-08 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 23:13 bugzilla-daemon [this message]
2021-05-08 23:24 ` [Bug 212999] xpad map Xbox 360 controller incorrect bugzilla-daemon
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=bug-212999-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.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).