All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Kondakov <virtuousfox@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Bastien Nocera <hadess@hadess.net>,
	Antonio Ospite <ospite@studenti.unina.it>,
	Szymon Janc <szymon.janc@gmail.com>
Subject: Reaching out again for serious bug in sixaxis plugin
Date: Tue, 14 Jul 2015 12:28:25 +0500	[thread overview]
Message-ID: <55A4BA19.6030109@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

Since both my attempts, in kernel bugzilla and here, were ignored and
you still don't have your own bugtracker I repeat my plea from
previously with plugin's authors CCed in hope that bug's existence at
least would be acknowledged.

Details are in http://article.gmane.org/gmane.linux.bluez.kernel/62305
Moreover, this livecd is almost identical to my running system which is
based on it, so it may be used to reproduce the glitch (antimicro,
jstest and evtest should help):
http://sourceforge.net/projects/hackeurs-sans-frontieres/files/0.8.1%20-%20The%20White%20Devil/Linux%20Live%20-%20HSF%20-%200.8.1_20150708.iso/download
If it could not be reproduce I'm afraid it may be a bug in handling my
BT controller.

Also, this kernel patch or a better alternative still hasn't been
applied and that's no good: https://patchwork.kernel.org/patch/1075972/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 278 bytes --]

             reply	other threads:[~2015-07-14  7:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  7:28 Sergey Kondakov [this message]
2015-07-14 11:32 ` Reaching out again for serious bug in sixaxis plugin Bastien Nocera
2015-07-14 16:54   ` simon
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=55A4BA19.6030109@gmail.com \
    --to=virtuousfox@gmail.com \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ospite@studenti.unina.it \
    --cc=szymon.janc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.