From: Mathieu Laurendeau <mathieu@laurendeau.net>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Missing BT_POWER option for l2cap sockets in bluetooth.h?
Date: Tue, 03 Dec 2013 18:46:21 +0100 [thread overview]
Message-ID: <529E18ED.3040701@laurendeau.net> (raw)
In-Reply-To: <20131203092228.GA9498@x220.p-661hnu-f1>
On Tue, Dec 03, 2013, Johan Hedberg wrote:
> What are you planning to use this for?
I'm working on a software [1] that can make a PC take the identity of a
Sixaxis and control a PS3 over bluetooth. It worked fine until kernel
3.1 from which there was a connection issue (a variable latency of at
least 4s). I tried tweaking the flush timeout, but it was not
concluding. Lately I took a look at the kernel source code and saw the
BT_POWER option was introduced in kernel 3.1. I turned it off and the
latency disappeared.
Thanks for the patch,
Mathieu
[1] https://github.com/matlo/GIMX
prev parent reply other threads:[~2013-12-03 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 20:22 Missing BT_POWER option for l2cap sockets in bluetooth.h? Mathieu Laurendeau
2013-12-03 9:22 ` Johan Hedberg
2013-12-03 17:46 ` Mathieu Laurendeau [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=529E18ED.3040701@laurendeau.net \
--to=mathieu@laurendeau.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@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