From: Marcel Holtmann <marcel@holtmann.org>
To: Andre Guedes <andre.guedes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 3/3] Bluetooth: Add MGMT_OP_SET_LE_SUPPORT command
Date: Tue, 21 Jun 2011 13:36:58 -0700 [thread overview]
Message-ID: <1308688620.2196.61.camel@aeonflux> (raw)
In-Reply-To: <1308686870-26101-3-git-send-email-andre.guedes@openbossa.org>
Hi Andre,
> This patch adds a new command to management interface to enable/
> disable LE support. This command will be used to set LE support
> according to the host configuration.
any reason why we want this separated and being under host stack control
in the first place. Should we not always enable LE if we can support it?
What are the reason to run an LE capable BlueZ on an LE capable dongle
and then not enable LE?
A similar argumentation applies for Secure Simple Pairing. We are
currently enabling this by default. Even while there are qualification
tests that would us force to run it with SSP disabled.
Maybe we should just have a generic kernel mgmt features enabling
command. One thing that I do not wanna do is to just blindly make a copy
of HCI commands for mgmt interface. The controller abstraction for the
mgmt interface is suppose to have a feature list so we can check what
the kernel supports and what not.
Regards
Marcel
next prev parent reply other threads:[~2011-06-21 20:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 20:07 [PATCH 1/3] Bluetooth: Add extfeatures to struct hci_dev Andre Guedes
2011-06-21 20:07 ` [PATCH 2/3] Bluetooth: Write LE Host Supported command complete event Andre Guedes
2011-06-21 20:07 ` [PATCH 3/3] Bluetooth: Add MGMT_OP_SET_LE_SUPPORT command Andre Guedes
2011-06-21 20:36 ` Marcel Holtmann [this message]
2011-06-22 16:36 ` Andre Guedes
2011-06-22 16:57 ` Marcel Holtmann
2011-06-22 18:33 ` Andre Guedes
2011-06-22 19:20 ` Gustavo F. Padovan
2011-06-22 20:00 ` Andre Guedes
2011-06-23 3:40 ` Marcel Holtmann
2011-06-21 21:27 ` [PATCH 1/3] Bluetooth: Add extfeatures to struct hci_dev Johan Hedberg
2011-06-22 2:16 ` Marcel Holtmann
2011-06-22 16:40 ` 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=1308688620.2196.61.camel@aeonflux \
--to=marcel@holtmann.org \
--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