From: Emil Lenngren <emil.lenngren@gmail.com>
To: Devin Bayer <dev@doubly.so>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
"Michael N. Moran" <mike@mnmoran.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: LE Advertising: Command Disallowed
Date: Wed, 11 Nov 2020 23:00:32 +0000 [thread overview]
Message-ID: <CAO1O6sefGxgwcesfu8qEFSX_HDRFFf8NW7ugyvXT=rSBVUMGYw@mail.gmail.com> (raw)
In-Reply-To: <cfee49fe-f4c1-e37a-64e2-94e2df927999@doubly.so>
Hi Devin,
Den ons 11 nov. 2020 kl 21:09 skrev Devin Bayer <dev@doubly.so>:
>
>
>
> On 11/11/2020 21.53, Luiz Augusto von Dentz wrote:
> >
> > You also need to ensure you are not mixing with extended advertisement
> > commands, iirc if the stack does send
> > BT_HCI_CMD_LE_READ_NUM_SUPPORTED_ADV_SETS it would already prevent the
> > legacy version to work. Bottom line here is, either use entire stack
> > or switch to user-channel with a proper stack, mixed handling won't
> > cut anymore, and for the most part we should be covering all the
> > advertisement features over D-Bus if we don't please let us know if
> > there are still gaps.
> >
>
> Hi Luiz,
>
> I am not sure what you mean about mixed handling, but I am not using bluetoothd.
> As you can see the entire log, I don't see any indication of
> BT_HCI_CMD_LE_READ_NUM_SUPPORTED_ADV_SETS. Could that be a default from boot
> that I need to disable?
>
> BTW, what is "user-channel with a proper stack" ?
>
> My issue with the D-BUS API is that I could never get reliable behavior of even
> basic discovering and connecting; it's not about missing features.
>
> ~ Devin
It would be good to see the complete log from when the "Reset" command
is issued, otherwise we don't know in which "state" the controller is
in at the various commands. Also widen the command window when running
btmon so we see the complete names. :)
Seeing the result from "LE Read Supported States" would also be nice.
/Emil
next prev parent reply other threads:[~2020-11-12 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 17:49 LE Advertising: Command Disallowed Devin Bayer
2020-11-11 20:04 ` Michael N. Moran
2020-11-11 20:11 ` Devin Bayer
2020-11-11 20:53 ` Luiz Augusto von Dentz
2020-11-11 21:07 ` Devin Bayer
2020-11-11 23:00 ` Emil Lenngren [this message]
2020-11-12 12:16 ` Devin Bayer
2020-11-12 13:53 ` Emil Lenngren
2020-11-12 16:24 ` Devin Bayer
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='CAO1O6sefGxgwcesfu8qEFSX_HDRFFf8NW7ugyvXT=rSBVUMGYw@mail.gmail.com' \
--to=emil.lenngren@gmail.com \
--cc=dev@doubly.so \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=mike@mnmoran.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.