From: Cameron Gutman <aicommander@gmail.com>
To: greenbigfrog@gmail.com, linux-input@vger.kernel.org
Cc: dmitry.torokhov@gmail.com
Subject: Re: X-Box One Controler (Covert Forces) no Input/Static Input
Date: Sat, 5 Dec 2015 23:56:42 -0800 [thread overview]
Message-ID: <5663EA3A.4050107@gmail.com> (raw)
In-Reply-To: 5662F0E0.7020806@gmail.com
I also have a Covert Forces Xbox One controller and can confirm this
issue. It looks like the 5 byte initialization packet used for rumble
support in various other Xbox One drivers (xboxdrv, forks of xpad) is
actually required for proper initialization of these new controllers.
Without it, we won't receive input data (as if initialization never
occurred at all).
Luckily, there's a trivial fix for this. We'll just send the larger
initialization packet, even without sending a sequence number in the
rumble packets yet. I've confirmed that this fixes the issue for me.
I'll send a patch shortly.
Cameron
next reply other threads:[~2015-12-06 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 7:56 Cameron Gutman [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-05 14:12 X-Box One Controler (Covert Forces) no Input/Static Input Jonathan Beilharz
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=5663EA3A.4050107@gmail.com \
--to=aicommander@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=greenbigfrog@gmail.com \
--cc=linux-input@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).