Re: [PATCH] Bluetooth: Support static address when BR/EDR has been disabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Marcel,

On Fri, Dec 19, 2014, Marcel Holtmann wrote:
> Every BR/EDR/LE dual-mode controller requires to have a public address
> and so far that has become the identity address and own address. The
> only way to change that behavior was with a force_static_address
> debugfs option.
> 
> However the host can actually disable the BR/EDR part of a dual-mode
> controller and turn into a single mode LE controller. In that case
> it makes perfect sense for a host to use a chosen static address
> instead of the public address.
> 
> So if the host disables BR/EDR and configures a static address, then
> that static address is used as identity address and own address. If
> the host does not configure a static address, then the public address
> is used as before.
> 
> Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx>
> ---
>  net/bluetooth/hci_core.c    | 8 +++++++-
>  net/bluetooth/hci_request.c | 8 +++++++-
>  2 files changed, 14 insertions(+), 2 deletions(-)

Applied to bluetooth-next. Thanks.

Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux