From: simon@mungewell.org
To: "Bastien Nocera" <hadess@hadess.net>
Cc: "Sergey Kondakov" <virtuousfox@gmail.com>,
linux-bluetooth@vger.kernel.org,
"Antonio Ospite" <ospite@studenti.unina.it>,
"Szymon Janc" <szymon.janc@gmail.com>
Subject: Re: Reaching out again for serious bug in sixaxis plugin
Date: Tue, 14 Jul 2015 12:54:37 -0400 [thread overview]
Message-ID: <a59e2e07885f3ee4bcb02cf370b3ff4c.squirrel@mungewell.org> (raw)
In-Reply-To: <1436873556.20249.50.camel@hadess.net>
>> Details are in
>> http://article.gmane.org/gmane.linux.bluez.kernel/62305
> The device is connected correctly via Bluetooth. Then the bug is in the
> device's input driver, which you could probably also see when it's
> connected via USB. The right forum for this is the linux-input mailing
As the original poster stated that this DOES NOT occur with a USB
connection, it does kind of point to a Bluetooth problem (or maybe with
device itself). Has anyone been able to replicate?
My suggestion would be to display/capture the hidraw interface and see if
the missing data is present there. This can be done as root with
--
$ hexdump -v -e '49/1 "%02x " "\n"' < /dev/hidraw0
--
The '49' is the byte count, and might be wrong (working from memory).
>> Also, this kernel patch or a better alternative still hasn't been
>> applied and that's no good:
>> https://patchwork.kernel.org/patch/1075972/
The multi-touch/many-axis stuff is a pain, but the linux-input list is the
place to discuss that...
Simon
next prev parent reply other threads:[~2015-07-14 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 7:28 Reaching out again for serious bug in sixaxis plugin Sergey Kondakov
2015-07-14 11:32 ` Bastien Nocera
2015-07-14 16:54 ` simon [this message]
2015-07-14 20:38 ` Sergey Kondakov
2015-07-15 5:29 ` Bastien Nocera
2015-07-15 7:54 ` Reaching out again for serious bug in sixaxis plugin & generic wireless transport with userspace daemon idea Sergey Kondakov
-- strict thread matches above, loose matches on Subject: below --
2015-07-15 5:52 Reaching out again for serious bug in sixaxis plugin simon
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=a59e2e07885f3ee4bcb02cf370b3ff4c.squirrel@mungewell.org \
--to=simon@mungewell.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ospite@studenti.unina.it \
--cc=szymon.janc@gmail.com \
--cc=virtuousfox@gmail.com \
/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).