From: Sergey Kondakov <virtuousfox@gmail.com>
To: simon@mungewell.org, Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Reaching out again for serious bug in sixaxis plugin & generic wireless transport with userspace daemon idea
Date: Wed, 15 Jul 2015 12:54:04 +0500 [thread overview]
Message-ID: <55A6119C.3020507@gmail.com> (raw)
In-Reply-To: <1436938182.20249.59.camel@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 3062 bytes --]
On 15.07.2015 10:52, simon@mungewell.org wrote:
> Oddly (or perhaps not) these 'funny' packets show up more frequently if I
> exercise the LEDs
> --
> root@blind-fury:/sys/class/leds/0005:054C:0268.0002::sony1#
> echo heartbeat > trigger
Tried that but with usb-host instead of heartbeat (which I don't have)
and wiggling mouse (which triggers the led). At first it's gone crazy
with 2-4 the frequency but when I tried to repeat it latter it was about
the same as always... still pretty frequent, every 10-30 seconds.
Sometimes 2 in short burst (1-5 seconds) with bigger pause.
> For reference this is seen with Bluez git, kernel 4.1rc7 on Xubuntu 15.04.
> I am unable to use 4.2 as there's another bug affecting me.
> I did not see this on 3.19 (stock kernel for system), but will recheck later.
> Simon
For me it was no less than entirety of bluez5 and kernel 3.x series, if
I recall.
On 15.07.2015 10:29, Bastien Nocera wrote:
> On Wed, 2015-07-15 at 01:38 +0500, Sergey Kondakov wrote:
> ...
>
> I skipped over the "technically accurate, all information provided
> technical description" to the "who gives a crap what this guy says, I'm
> not going to help him anyway".
>
> Which I didn't read, maybe?
Which illustrates my point exactly.
> Whatever contributions you might have made in the past, or will in the
> future, insulting people's work will only get you so far.
>
Ignoring glitches will diminish your work, hurt all users and make it
look for everyone precisely in a way that I described.
Imagine what happened when distributions started to move (openSUSE at
least) bluez4->bluez5 while it didn't have any GUI whatsoever and was
still quite new... with no place to even properly complain (of course
distributions would send you to upstream and do nothing themselves).
"Wanna use some BT ? Better tech-up and go on a quest !"
Some (again, openSUSE) even still disable sixaxis plugin in their
packages. And properly rebuilding packages for binary distributions is a
pain. "Wanna play some games ? Screw you !"
BT support in all OSes seem to be treated with afterthought. Windows
even didn't have its own bluetooth stack until recently, I think. I
applaud any efforts to do it properly for Linux but your own attitude
don't exactly make it any easier either.
And BT standard itself is a mess that breaks OSI, you can't deny that.
Actually, seeing how any serious wireless devices use a helper device
(usually USB transponder with direct USB connection emulation) for
transporting their data (gaming mouses, pro-headphones, "hdmi video
transmitters") makes me think that if someone would come up with
userspace drivers that would replace usual USB emulation methods for
those and allow getting and sending data directly from user's wifi card
in a secure, defined and standardized (preferably by IEEE) way then BT
may go obsolete altogether. Such implementation may even be completely
data link (or even network) neutral for compatibility with any
underlying networking type.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 278 bytes --]
prev parent reply other threads:[~2015-07-15 7:54 UTC|newest]
Thread overview: 6+ 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
2015-07-14 20:38 ` Sergey Kondakov
2015-07-15 5:29 ` Bastien Nocera
2015-07-15 7:54 ` Sergey Kondakov [this message]
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=55A6119C.3020507@gmail.com \
--to=virtuousfox@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon@mungewell.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).