linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Serge van den Boom <serge@vdboom.org>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Registering profile or making discoverable resets adapter class
Date: Mon, 1 Aug 2016 17:13:32 +0300	[thread overview]
Message-ID: <CABBYNZJMMSrgRO8EsZ78yOv0R5cwfpz65EQ+-zSV67mX2ee4Dw@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.00.1608011427420.69212@toad.stack.nl>

Hi Serge,

On Mon, Aug 1, 2016 at 3:34 PM, Serge van den Boom <serge@vdboom.org> wrote:
> Hi,
>
> When a new profile is registered, or an adapter is make discoverable,
> the device class of the adapter is reset to the value set in
> /etc/bluetooth/main.conf.
>
> The test case below (to be run as root) demonstrates the issue. For this
> demonstration, there should be no 'Class = ...' setting in
> /etc/bluetooth/main.conf.

This is a classical problem of using hci* tools along with bluetoothd,
they both are trying to control the same thing and then you got a
conflict, it shall be one or the other but not both. If you are
curious to look at the bluetoothd source code you will see that the we
derive the class of the device from the registered services so there
is no point in doing anything with hcitool.

  reply	other threads:[~2016-08-01 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 12:34 Registering profile or making discoverable resets adapter class Serge van den Boom
2016-08-01 14:13 ` Luiz Augusto von Dentz [this message]
2016-08-01 16:12   ` Serge van den Boom
2016-08-01 18:52     ` Luiz Augusto von Dentz
2016-08-02  8:53       ` Serge van den Boom

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=CABBYNZJMMSrgRO8EsZ78yOv0R5cwfpz65EQ+-zSV67mX2ee4Dw@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=serge@vdboom.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).