Bluetooth: Host: Deprecate auto name in AD
Deprecate the advertiser options `BT_LE_ADV_OPT_USE_NAME` and `BT_LE_ADV_OPT_FORCE_NAME_IN_AD`. Reasons: - It is out of place in the advertiser options, as it acts on advertising data and not configuration - The behavior is not clear. All of these are trick questions: - where does the data for the name go? - do I have to allocate memory for this? - does it work the same in legacy vs extended advertising? - The trade-off between UX improvement and extra complexity in the host is debatable. Hundreds of lines in the stack to avoid making the user type out less than ten. Also deprecate the following macros that uses those options: - `BT_LE_ADV_CONN_NAME` - `BT_LE_ADV_CONN_NAME_AD` - `BT_LE_ADV_NCONN_NAME` - `BT_LE_EXT_ADV_CONN_NAME` - `BT_LE_EXT_ADV_SCAN_NAME` - `BT_LE_EXT_ADV_NCONN_NAME` - `BT_LE_EXT_ADV_CODED_NCONN_NAME` Update the migration guide and the release note for Zephyr 3.7 to describe those changes. Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no>
This commit is contained in:
parent
f461ae574f
commit
909ad8170c
3 changed files with 113 additions and 32 deletions
|
@ -208,6 +208,20 @@ Bluetooth Classic
|
|||
Removed the :kconfig:option:`CONFIG_BT_BREDR`. It is replaced by new option
|
||||
:kconfig:option:`CONFIG_BT_CLASSIC`. (:github:`69651`)
|
||||
|
||||
Bluetooth Host
|
||||
==============
|
||||
|
||||
* The advertiser options :code:`BT_LE_ADV_OPT_USE_NAME` and :code:`BT_LE_ADV_OPT_FORCE_NAME_IN_AD`
|
||||
are deprecated in this release. The application need to include the device name explicitly. One
|
||||
way to do it is by adding the following to the advertising data or scan response data passed to
|
||||
the host:
|
||||
|
||||
.. code-block:: c
|
||||
|
||||
BT_DATA(BT_DATA_NAME_COMPLETE, CONFIG_BT_DEVICE_NAME, sizeof(CONFIG_BT_DEVICE_NAME) - 1)
|
||||
|
||||
(:github:`71686`)
|
||||
|
||||
Networking
|
||||
**********
|
||||
|
||||
|
|
|
@ -28,6 +28,27 @@ https://docs.zephyrproject.org/latest/security/vulnerabilities.html
|
|||
* CVE-2024-3077 `Zephyr project bug tracker GHSA-gmfv-4vfh-2mh8
|
||||
<https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-gmfv-4vfh-2mh8>`_
|
||||
|
||||
API Changes
|
||||
***********
|
||||
|
||||
Deprecated in this release
|
||||
==========================
|
||||
|
||||
* Bluetooth advertiser options :code:`BT_LE_ADV_OPT_USE_NAME` and
|
||||
:code:`BT_LE_ADV_OPT_FORCE_NAME_IN_AD` are now deprecated. That means the following macro are
|
||||
deprecated:
|
||||
|
||||
* :c:macro:`BT_LE_ADV_CONN_NAME`
|
||||
* :c:macro:`BT_LE_ADV_CONN_NAME_AD`
|
||||
* :c:macro:`BT_LE_ADV_NCONN_NAME`
|
||||
* :c:macro:`BT_LE_EXT_ADV_CONN_NAME`
|
||||
* :c:macro:`BT_LE_EXT_ADV_SCAN_NAME`
|
||||
* :c:macro:`BT_LE_EXT_ADV_NCONN_NAME`
|
||||
* :c:macro:`BT_LE_EXT_ADV_CODED_NCONN_NAME`
|
||||
|
||||
Application developer will now need to set the advertised name themselves by updating the advertising data
|
||||
or the scan response data.
|
||||
|
||||
Architectures
|
||||
*************
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue