linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Clément Jacquemin" <clement.jacquemin@epita.fr>
To: <linux-bluetooth@vger.kernel.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>
Subject: Re: Connection handler and btmgmt/bluetoothctl
Date: Sun, 11 Sep 2016 23:46:06 +0200	[thread overview]
Message-ID: <57D5D09E.7080801@epita.fr> (raw)
In-Reply-To: <20160713055005.GA30167@t440s.P-661HNU-F1>

Thanks for your answer Johan!

Le 13/07/2016 07:50, Johan Hedberg a écrit :
> On Tue, Jul 12, 2016, Clément Jacquemin wrote:
>> Another question about best practice. For the moment I use "btmgmt" to
>> configure my daemon. However, the "bluetoothctl" binary seems to be a more
>> stable alternative except that i cannot find any way to do the "le on"
>> command as in "btmgmt".
>> Is there any way to activate the low energy option with bluetoothctl?
>
> bluetoothctl talks to bluetoothd and bluetoothd already automatically
> enables LE support whenever it's reported to be supported by the kernel.
>
> Johan

I still have some questions.

First, is there any equivalent of the 'bt_gatt_server_send_notification' 
method from "src/shared/gatt-server.c" but with the GATT D-BUS API. I 
did not find anything about that.

Second, when one of my characteristic need more than 5 seconds to 
process the data, the client is systematically disconnect 5 seconds 
after requesting a read action on that characteristic. I suppose there 
is a timeout configuration somewhere, but where ?

Clément.

  reply	other threads:[~2016-09-11 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12  0:29 Connection handler and btmgmt/bluetoothctl Clément Jacquemin
2016-07-13  5:50 ` Johan Hedberg
2016-09-11 21:46   ` Clément Jacquemin [this message]
2016-10-17 23:37     ` Clément Jacquemin

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=57D5D09E.7080801@epita.fr \
    --to=clement.jacquemin@epita.fr \
    --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;
as well as URLs for NNTP newsgroup(s).