Home
last modified time | relevance | path

Searched refs:rely (Results 26 – 50 of 58) sorted by relevance

123

/Zephyr-latest/doc/services/sensing/
Dindex.rst21 Virtual sensors rely on other sensor objects (physical or virtual) as
/Zephyr-latest/doc/develop/west/
Dworkspaces.rst41 an implementation detail; users should not rely on these refs' existence or
Drelease-notes.rst186 modules may rely on.
670 West now requires Python 3.6 or later. Additionally, some features may rely on
/Zephyr-latest/cmake/modules/
Ddts.cmake35 # We rely on the C preprocessor, the devicetree python package, and
/Zephyr-latest/boards/acrn/acrn/doc/
Dindex.rst245 This means that we must rely on GRUB's filesystem driver. The three
/Zephyr-latest/doc/connectivity/networking/api/
Dhttp_server.rst126 HTTPS services rely on TLS credentials being registered in the system.
/Zephyr-latest/doc/security/
Dsecure-coding.rst105 - **Complementary Security/Defense in Depth**: do not rely on a single
Dsecurity-overview.rst235 Some of these categories are interconnected and rely on multiple pieces
327 - **Complementary Security/Defense in Depth:** do not rely on a single
/Zephyr-latest/doc/build/dts/
Dtroubleshooting.rst30 Many Zephyr header files rely on information from devicetree, so including some
/Zephyr-latest/doc/build/kconfig/
Dsetting.rst208 but do not want to rely directly on the common symbol. For example, you might
/Zephyr-latest/doc/develop/getting_started/
Dindex.rst162 These instructions rely on `Chocolatey`_. If Chocolatey isn't an option,
/Zephyr-latest/boards/snps/nsim/arc_classic/doc/
Dindex.rst212 It is strongly recommended to not rely on the mdb command line options listed above but
/Zephyr-latest/modules/mbedtls/
DKconfig.tls-generic535 MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG is by default limited to rely only
/Zephyr-latest/subsys/bluetooth/host/
DKconfig375 but want to rely on the remote device to initiate the procedure at its
395 supported but want to rely on the remote device to initiate the
/Zephyr-latest/doc/releases/
Dmigration-guide-3.7.rst287 ``sample-point-data`` devicetree properties (or rely on
318 either fail initialization or rely on automatic bus-off recovery. Having this as a mode
Drelease-notes-1.7.rst329 * ``ZEP-1483`` - H:4 HCI driver (h4.c) should rely on UART flow control to avoid dropping packets
Dmigration-guide-3.6.rst483 buffers get by default one byte of headroom now, which HCI transport implementations can rely on
Drelease-notes-3.5.rst2179 the system using ZBus, making post-definition channel observation rely on the stack instead of
2184 * ZBus runtime observers now rely on the heap instead of a memory pool.
/Zephyr-latest/doc/hardware/porting/
Darch.rst38 * **Utility libraries**: some common kernel APIs rely on a
962 GDB will then rely on software breakpoints.
Dboard_porting.rst715 nor should it rely upon special system setup/configuration. For example; do
/Zephyr-latest/doc/kernel/services/threads/
Dindex.rst102 and not rely on signaling from within application logic.
/Zephyr-latest/doc/services/storage/zms/
Dzms.rst287 Using storage systems that rely on an erase-value (NVS as an example) will need to emulate the
/Zephyr-latest/doc/services/logging/
Dindex.rst349 In case of error condition system usually can no longer rely on scheduler or
/Zephyr-latest/doc/connectivity/bluetooth/api/audio/
Dbluetooth-le-audio-arch.rst1257 and the LE Audio contributors almost only rely on the automated workflows
/Zephyr-latest/doc/contribute/
Dguidelines.rst201 tools yourself, you will need to rely on the Continuous Integration (CI)

123