Home
last modified time | relevance | path

Searched refs:resolving (Results 1 – 17 of 17) sorted by relevance

/Zephyr-Core-3.7.0/subsys/bluetooth/host/classic/
Dbr.c261 uint8_t resolving; member
352 priv->resolving = 1U; in report_discovery_results()
507 priv->resolving = 0U; in bt_hci_remote_name_request_complete()
559 if (dpriv->resolving) { in bt_hci_remote_name_request_complete()
963 if (!priv->resolving) { in bt_br_discovery_stop()
/Zephyr-Core-3.7.0/doc/connectivity/networking/api/
Dnet_shell.rst7 enabling/disabling features, and issuing commands like ping or DNS resolving.
/Zephyr-Core-3.7.0/doc/connectivity/networking/
Doverview.rst140 or DNS resolving. The net-shell is useful when developing network software.
/Zephyr-Core-3.7.0/doc/contribute/
Dcontributor_expectations.rst209 defines the following escalation process for resolving technical disagreements.
/Zephyr-Core-3.7.0/doc/build/kconfig/
Dsetting.rst309 for **ANY** definition result in the symbol resolving to ``y``, the symbol
/Zephyr-Core-3.7.0/doc/develop/west/
Dmanifest.rst1284 :ref:`resolving your manifest <west-manifest-resolve>` to see the final results
1420 :file:`zephyr/west.yml` entirely when resolving imports. West always uses the
1479 resolving imports.
2047 The ultimate outcomes of resolving manifest imports are:
Drelease-notes.rst608 files, resolving the results into a single logical manifest.
/Zephyr-Core-3.7.0/subsys/bluetooth/controller/
DKconfig.ll_sw_split1153 be used in resolving collisions.
1190 feature, which eliminates priorities and collision resolving in the
/Zephyr-Core-3.7.0/doc/releases/
Drelease-notes-2.4.rst657 * Fixed DNS resolving by ignoring incoming queries while we are resolving a name.
1068 * :github:`27931` - Address resolving when eswifi is used causes MPU FAULT
1069 * :github:`27929` - Address resolving when eswifi is used causes MPU FAULT
Drelease-notes-2.2.rst918 * :github:`21970` - net: dns: mDNS resolving fails when responder is also enabled
Drelease-notes-2.3.rst1194 * :github:`23226` - Bluetooth: host: Peer not resolved when host resolving is used
Drelease-notes-2.0.rst530 * :github:`18732` - net: mDNS name resolving issue between 2 Zephyr nodes
Drelease-notes-2.5.rst620 * Added resolving literal IP addresses even when DNS is disabled.
Drelease-notes-3.1.rst1338 * :github:`45827` - bluetooth: bluetooth host: Adding the same device to resolving list
Drelease-notes-3.2.rst2448 * :github:`45827` - bluetooth: bluetooth host: Adding the same device to resolving list
/Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/audio/
Dbluetooth-le-audio-arch.rst1210 The Coordinated Set Identification Service (CSIS) may encrypt the SIRK (set identity resolving key).
/Zephyr-Core-3.7.0/subsys/bluetooth/host/
DKconfig407 identity resolving keys (IRK) and store them in the settings subsystem.