Searched full:rest (Results 1 – 25 of 214) sorted by relevance
123456789
| /Zephyr-latest/subsys/secure_storage/src/its/ |
| D | CMakeLists.txt | 17 This means that the data and keys stored via the PSA APIs may not be secure at rest.")
22 This means that the data and keys stored via the PSA APIs will not be secure at rest.
|
| /Zephyr-latest/tests/kernel/fatal/exception/ |
| D | README | 4 thread, the thread gets aborted and the rest of the system executes normally.
|
| /Zephyr-latest/doc/services/ |
| D | secure_storage.rst | 23 may secure the data stored via the PSA Secure Storage API at rest.
37 * does not guarantee that the data it stores will be secure at rest in all cases.
60 However, this does not guarantee that the data stored will be secure at rest in all cases,
72 It is only secured at rest. Protecting it at runtime as well
|
| /Zephyr-latest/arch/arm/core/cortex_m/ |
| D | vector_table.S | 17 * rest should not be triggered until the kernel is ready to handle them.
37 * switching to the interrupt stack for the rest of the early boot
|
| /Zephyr-latest/doc/services/pm/ |
| D | overview.rst | 11 Thus a coherent abstraction is presented to the rest of the OS and the application layer.
|
| /Zephyr-latest/boards/actinius/common/ |
| D | actinius_board_common.c | 77 /* do not return so that the rest of the init process is attempted */ in actinius_board_init()
85 /* do not return so that the rest of the init process is attempted */ in actinius_board_init()
|
| /Zephyr-latest/arch/arm/core/ |
| D | header.S | 16 * switching to the interrupt stack for the rest of the early boot
|
| /Zephyr-latest/modules/mbedtls/ |
| D | Kconfig | 75 even for HTTPS REST API, the payload can be limited to max size of
76 (REST request, REST response, server certificate(s)).
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.wncm14a2a | 28 to the rest of the network stack, letting the rx thread continue
|
| D | Kconfig.quectel-bg9x | 30 to the rest of the network stack, letting the rx thread continue
|
| D | Kconfig.ublox-sara-r4 | 52 to the rest of the network stack, letting the rx thread continue
|
| /Zephyr-latest/tests/bsim/bluetooth/ |
| D | compile.sh | 17 # the rest to save a couple of seconds.
|
| /Zephyr-latest/arch/nios2/core/ |
| D | thread.c | 49 /* Leave the rest of thread->callee_saved junk */ in arch_new_thread()
|
| /Zephyr-latest/doc/services/binary_descriptors/ |
| D | index.rst | 46 (currently uint, string or bytes), and the rest is the ID. The ID is globally unique to each
148 The rest of the API is agnostic to where the data is. After the handle has been initialized,
149 it can be used with the rest of the API:
|
| /Zephyr-latest/samples/tfm_integration/psa_crypto/src/ |
| D | util_app_cfg.h | 19 * firmware updates, since they can be used to identify to layout of the rest
|
| /Zephyr-latest/doc/develop/west/ |
| D | moving-to-west.rst | 49 #. Clone the rest of the repositories used by zephyr::
|
| /Zephyr-latest/arch/arm/include/cortex_m/ |
| D | stack.h | 57 * for Cortex-M3 and Cortex-M4 (ARMv7-M) MCUs. For the rest in z_arm_interrupt_stack_setup()
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 003_rfc-proposal.md | 47 Highlight how the change may affect the rest of the project (new components,
|
| /Zephyr-latest/scripts/ |
| D | make_bugs_pickle.py | 33 - GitHub API: https://docs.github.com/en/rest
|
| /Zephyr-latest/doc/_extensions/zephyr/doxytooltip/static/ |
| D | doxytooltip.css | 3 look and feel that's consistent with the rest of the documentation without necessarily aiming
|
| /Zephyr-latest/dts/bindings/watchdog/ |
| D | nxp,fs26-wdog.yaml | 12 state. This driver covers only the watchdog functionality of FS26. The rest
|
| /Zephyr-latest/subsys/testsuite/ztest/src/ |
| D | ztest_defaults.c | 14 * removes the current directory from the filename and returns the rest.
|
| /Zephyr-latest/.github/workflows/ |
| D | scorecards.yml | 41 # Publish results to OpenSSF REST API for easy access by consumers.
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | guidelines.rst | 29 This document provides a quick reference for commonly used reST and
39 Indenting is significant in reST file content, and using spaces is
60 While reST allows use of both an overline and matching underline to
98 item and has more than one line of reST text. Additional lines
107 #. It has three items (and uses autonumbering for the rest of the list)
120 to document a word or phrase with an explanation. For example this reST
353 Some common reST inline markup samples:
366 Sphinx extends reST by supporting additional inline markup elements (called
424 of the reST files. The names of these replacement characters are the same as used in HTML
437 Use the reST :rst:dir:`code-block` directive to create a highlighted block of
[all …]
|
| /Zephyr-latest/samples/subsys/llext/modules/ |
| D | README.rst | 39 - By default, the sample will compile the function along with the rest of
|
123456789
