linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Serge van den Boom <serge@vdboom.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
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 18:12:01 +0200 (CEST)	[thread overview]
Message-ID: <alpine.BSF.2.00.1608011632330.96508@toad.stack.nl> (raw)
In-Reply-To: <CABBYNZJMMSrgRO8EsZ78yOv0R5cwfpz65EQ+-zSV67mX2ee4Dw@mail.gmail.com>

Hi Luiz,

Thanks for the reply.

On Mon, 1 Aug 2016, Luiz Augusto von Dentz wrote:
> 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.

That is interesting, because if I don't set the class explicitly, it
always shows up as 0x100000 when I inspect it. And more relevantly,
if I don't explicitly set the class, the (HID) device that I am
implementing won't be discovered.

I haven't been able to find the part of the bluetoothd code that you are
referring to, so far. I would appreciate it if you could point me in the
right direction.


Thanks,

Serge


  reply	other threads:[~2016-08-01 16:12 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
2016-08-01 16:12   ` Serge van den Boom [this message]
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=alpine.BSF.2.00.1608011632330.96508@toad.stack.nl \
    --to=serge@vdboom.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@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;
as well as URLs for NNTP newsgroup(s).