Searched refs:require (Results 251 – 275 of 315) sorted by relevance
1...<<111213
| /Zephyr-latest/samples/net/mqtt_publisher/ |
| D | README.rst | 143 sample to connect to it, it does require some work on the user's part to
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 300 toolchains for all Zephyr target architectures, and does not require any extra
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 354 TraceRecorder repo (e.g. lwIP), although they might require modifications to work with Zephyr.
590 Unfortunately, I/O may not be atomic and may, therefore, require locking.
|
| /Zephyr-latest/doc/contribute/ |
| D | external.rst | 154 This may require adding an entry in the :file:`MAINTAINERS.yml` as part of the
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | images.rst | 336 ``ExternalZephyrProject_Add()`` require changes to sysbuild code in Zephyr. This should only be
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 183 Depending on the scope of this task this might require additional help from
|
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 219 ensure that key material is available to regions that require it, but not to
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net_config_guide.rst | 201 then this value might require finetuning (lowering), otherwise multiple
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 307 either ``DEP1`` **OR** ``DEP2`` are true, it does not require both:
|
| /Zephyr-latest/boards/snps/hsdk/doc/ |
| D | index.rst | 236 shields do not require this ICSP header as the SPI master interface on this ICSP header
|
| /Zephyr-latest/boards/snps/hsdk4xd/doc/ |
| D | index.rst | 233 shields do not require this ICSP header as the SPI master interface on this ICSP header
|
| /Zephyr-latest/subsys/debug/ |
| D | Kconfig | 356 automatically but only if the architecture does not require if for
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 184 will require ``app`` to be built with Zephyr 2.2.0 as minimum.
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 58 operations that require a device to remain powered on. In such cases,
|
| /Zephyr-latest/doc/develop/tools/ |
| D | coccinelle.rst | 280 require external tools for indexing the code. None of them is
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | main.rst | 209 Many network interfaces require a network association procedure to be completed before being usable.
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | Kconfig.tfm | 130 As isolation levels 2 and 3 require PSA_API (TFM_IPC) support,
|
| /Zephyr-latest/samples/subsys/mgmt/updatehub/ |
| D | README.rst | 41 * It is important understand that some wireless technologies may require a
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig | 338 net-shell require also some smaller amount of memory.
810 Used for self-contained networking tests that do not require a
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 142 The Zephyr integration tools require a proper Linux environment and
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 304 that may require multiple blocking operations on underlying kernel
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 126 require a refill exception of its own.
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 175 areas of the codebase with a proper justification. Exception would require
|
| /Zephyr-latest/boards/espressif/esp_wrover_kit/doc/ |
| D | index.rst | 589 require no external hardware and are debuggable as-is. The JTAG
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.7.rst | 866 to ``VIRTUAL``. This could require changes to the code that sets the VLAN tags to a network
949 * The :ref:`POSIX API Kconfig deprecations <zephyr_3.7_posix_api_deprecations>` may require
|
1...<<111213
