From: Johan Hedberg <johan.hedberg@gmail.com>
To: Andre Guedes <andre.guedes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Don't set LE flags in mgmt_start_discovery()
Date: Tue, 22 Nov 2011 23:58:22 +0200 [thread overview]
Message-ID: <20111122215822.GA23550@fusion.localdomain> (raw)
In-Reply-To: <1321991470-2201-1-git-send-email-andre.guedes@openbossa.org>
Hi Andre,
On Tue, Nov 22, 2011, Andre Guedes wrote:
> Since LE based discovery procedures are not yet supported, we should
> not set the LE flags in mgmt_start_discovery(). Otherwise, we might
> get an error from management interface.
> ---
> plugins/mgmtops.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/plugins/mgmtops.c b/plugins/mgmtops.c
> index b9e9ad6..d28f89c 100644
> --- a/plugins/mgmtops.c
> +++ b/plugins/mgmtops.c
> @@ -1689,8 +1689,6 @@ static int mgmt_start_discovery(int index)
> hdr->index = htobs(index);
>
> hci_set_bit(MGMT_ADDR_BREDR, &cp->type);
> - hci_set_bit(MGMT_ADDR_LE_PUBLIC, &cp->type);
> - hci_set_bit(MGMT_ADDR_LE_RANDOM, &cp->type);
>
> if (write(mgmt_sock, buf, sizeof(buf)) < 0)
> return -errno;
Since setting these bits is what user space needs to do anyway in the
long run I don't thing it's worth to remove them temporarily. Instead
I'd just make the kernel modifications initially so that an error is
only triggered of MGMT_ADDR_BREDR isn't set and in other cases just do
normal BR/EDR discovery (and ignore the LE bits).
Johan
next prev parent reply other threads:[~2011-11-22 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 19:51 [PATCH] Don't set LE flags in mgmt_start_discovery() Andre Guedes
2011-11-22 21:58 ` Johan Hedberg [this message]
2011-11-24 18:06 ` Andre Guedes
2011-11-24 18:22 ` Johan Hedberg
2011-11-24 18:29 ` Anderson Lizardo
2011-11-24 18:44 ` Andre Guedes
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=20111122215822.GA23550@fusion.localdomain \
--to=johan.hedberg@gmail.com \
--cc=andre.guedes@openbossa.org \
--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