Linux bluetooth development
 help / color / mirror / Atom feed
From: Andrejs Hanins <andrejs.hanins@ubnt.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Tim Tisdall <tisdall@gmail.com>, linux-bluetooth@vger.kernel.org
Subject: Re: bt dongle goes awry after too many connections
Date: Mon, 09 Mar 2015 18:47:56 +0200	[thread overview]
Message-ID: <54FDCEBC.2050705@ubnt.com> (raw)
In-Reply-To: <185295B8-ABD9-4EDF-B290-12C430CCA906@holtmann.org>

Hi Marcel,
On 2015.03.09. 18:21, Marcel Holtmann wrote:
> Hi Andrejs,
>
>>>> If you do not need BR/EDR, you can switch that off and it might free the radio resources you need for the many LE connections.
>>> Would someone please tell me how you do that?  I haven't seen this
>>> being done before.  Is it an HCI command?  ioctl command to the
>>> kernel?
>> ControllerMode = le
>> in /etc/bluetooth/main.conf
> which might at least need a 3.13.x kernel to actually work correctly. While the API is there, we have made significant fixes to the LE only mode in later kernels. Using a dual-mode controller in LE only mode actually needed some extra care.
>
> As I said, if it is not 3.18.x or 3.19.x kernel, then personally I would not bet on it. We have made sure that bug fixes are put into the -stable kernels for these release. Anything older has no guarantee anymore.
Sure, I noticed that lots of work has been done lately in regard to LE, 
so I'm indeed using 5.28 daemon@3.19.x kernel in LE-only mode and so far 
so good.
One of the useful things which still seems to be missing is the control 
over LE advertisements via D-Bus iface. "Discoverable" property change 
does not affect LE advs. I'm currently using 'hciconfig hci0 leadv' to 
make it work. But still, LE advs stop and do not re-start after adapter 
is connected/disconnected to some peripheral.
>
> Regards
>
> Marcel
>

  reply	other threads:[~2015-03-09 16:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 20:25 bt dongle goes awry after too many connections Tim Tisdall
2015-03-03  0:17 ` Marcel Holtmann
2015-03-03 16:02   ` Tim Tisdall
2015-03-03 16:07     ` Tim Tisdall
2015-03-03 16:19     ` Marcel Holtmann
2015-03-03 16:41       ` Tim Tisdall
2015-03-09 14:40         ` Tim Tisdall
2015-03-09 15:27           ` Andrejs Hanins
2015-03-09 16:21             ` Marcel Holtmann
2015-03-09 16:47               ` Andrejs Hanins [this message]
2015-03-09 16:53                 ` Tim Tisdall
2015-03-09 16:59                   ` Andrejs Hanins
2015-03-09 17:10                 ` Marcel Holtmann
2015-03-09 17:22                   ` Andrejs Hanins
  -- strict thread matches above, loose matches on Subject: below --
2015-03-02 20:41 Tim Tisdall

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=54FDCEBC.2050705@ubnt.com \
    --to=andrejs.hanins@ubnt.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=tisdall@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