Home
last modified time | relevance | path

Searched refs:doing (Results 51 – 75 of 113) sorted by relevance

12345

/Zephyr-latest/arch/xtensa/core/
DREADME_MMU.txt124 requires doing a fetch via the instruction TLB. And that obviously
169 (to avoid doing memory access at inopportune moments).
185 doing data accesses yet (including refills), and will resolve the
262 notifying another CPU of changes to page mappings beyond doing
/Zephyr-latest/samples/net/sockets/big_http_download/
DREADME.rst60 If you are doing extensive testing with this sample, please reference
/Zephyr-latest/subsys/net/lib/dns/
DKconfig198 By doing so, Zephyr network services are discoverable
208 Chapter 9. By doing so, Zephyr network services are discoverable
/Zephyr-latest/doc/services/rtio/
Dindex.rst14 RTIO provides a framework for doing asynchronous operation chains with event
29 This means doing complex audio, video, or sensor streaming requires direct
/Zephyr-latest/drivers/serial/
DKconfig92 doing and promise not to file bug when things do not work out.
/Zephyr-latest/cmake/modules/
DFindZephyr-sdk.cmake29 # any Sdk. This can be used to fetch available Zephyr-SDKs before doing
/Zephyr-latest/modules/hal_nordic/nrfx/
DCMakeLists.txt165 # doing the proper configuration sequence during system init
/Zephyr-latest/lib/libc/picolibc/
DKconfig153 doing binary to decimal conversion in printf for 64-bit
/Zephyr-latest/arch/posix/
DCMakeLists.txt83 # While doing the partial linking of the native library, some symbols will be missing
/Zephyr-latest/subsys/bluetooth/common/
DKconfig301 the 'btmon' tool from BlueZ is capable of doing this.
320 the 'btmon' tool from BlueZ is capable of doing this.
/Zephyr-latest/modules/hal_nordic/
DKconfig114 you know what you are doing.
/Zephyr-latest/doc/build/dts/
Dtroubleshooting.rst15 .. important:: Try this first, before doing anything else.
299 To prevent the compiler from doing this, you can disable the
/Zephyr-latest/drivers/modem/
DKconfig.hl7800298 Do not mess with it unless you know what you are doing.
/Zephyr-latest/tests/ztest/error_hook/
DREADME.txt10 Why doing this
/Zephyr-latest/kernel/
DKconfig.vm25 just one RAM region and doing this makes linking much simpler, as
/Zephyr-latest/doc/develop/flash_debug/
Dnordic_segger.rst186 messages by doing the following:
/Zephyr-latest/doc/kernel/services/other/
Dfatal.rst174 and doing so will generate a kernel oops instead. Otherwise, the fatal error
/Zephyr-latest/doc/connectivity/networking/
Dnetwork_monitoring.rst139 ``net capture setup`` command for doing that. The command syntax is
/Zephyr-latest/doc/kernel/memory_management/
Dheap.rst126 application-provided callback is responsible for doing the underlying
/Zephyr-latest/doc/develop/test/
Dpytest.rst310 hardwares). If anyone is interested in doing this for some reasons (for example via
/Zephyr-latest/arch/arm/core/
DKconfig265 threads many not be context-switched-out while doing a Secure
/Zephyr-latest/subsys/bluetooth/
DKconfig.logging25 # The downside of doing that is that people need to be careful when adding a new
/Zephyr-latest/doc/kernel/usermode/
Dkernelobjects.rst19 dereference these addresses, doing so will cause a memory protection fault.
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dcap.rst191 When doing broadcast
/Zephyr-latest/doc/services/smf/
Dindex.rst35 For example instead of doing this ``(struct smf_ctx *)&user_obj``, you could

12345