Searched refs:there (Results 226 – 250 of 423) sorted by relevance
12345678910>>...17
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | lifos.rst | 113 With this API, there is no need to reserve space for the kernel's use in
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | networking_with_multiple_instances.rst | 37 As there are multiple ways to setup the Zephyr network, the example below uses
|
| /Zephyr-latest/doc/develop/west/ |
| D | without-west.rst | 95 # cd into zephyrproject if not already there
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | x86.rst | 45 is done at the page directory level, there is no need to allocate
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | mpsc_pbuf.rst | 8 packets are stored in the buffer. Packet buffer works under assumption that there
|
| /Zephyr-latest/boards/weact/blackpill_f401ce/doc/ |
| D | index.rst | 91 Note on SPI pin mapping: According to the `board release notes`_, there was a brief
|
| /Zephyr-latest/boards/weact/blackpill_f411ce/doc/ |
| D | index.rst | 91 Note on SPI pin mapping: According to the `board release notes`_, there was a brief
|
| /Zephyr-latest/samples/subsys/shell/fs/ |
| D | README.rst | 134 During the transfer there are printed messages indicating how many chunks are
|
| /Zephyr-latest/samples/modules/thrift/hello/ |
| D | README.rst | 110 Additionally, there is a ``hello_client.py`` Python script that can be used
|
| /Zephyr-latest/doc/services/pm/ |
| D | power_domain.rst | 53 be turned on or off to reduce power consumption. But there is a
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr.rst | 34 Additionally, there is a :zephyr:code-sample:`sample <smp-svr>` server that provides
|
| /Zephyr-latest/doc/build/signing/ |
| D | index.rst | 6 Binaries can be optionally signed as part of a build automatically using CMake code, there is
|
| /Zephyr-latest/doc/build/version/ |
| D | index.rst | 38 field to a single byte (note that there may be further restrictions depending upon what the version
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister_statuses.rst | 49 despite them being called "Suites" there.
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 52 time by a system binary (ld-linux.so). But there is no ld-linux.so in
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf5340bsim.rst | 120 * Currently there is no model of the SPU, and therefore neither flash, RAM areas or peripherals
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.smp | 110 when this is selected, there is an implicit API change that
|
| /Zephyr-latest/samples/subsys/logging/syst/ |
| D | README.rst | 54 Since the output is being directed to a text file, there will not be
225 Since the output is being directed to a text file, there will not be
|
| /Zephyr-latest/doc/services/rtio/ |
| D | index.rst | 44 API from the Linux kernel provides a winning model. In io_uring there are two
94 In order to know when a sqe has completed there is a completion
|
| /Zephyr-latest/doc/services/settings/ |
| D | index.rst | 49 effect right away, for example if there are multiple settings
153 changes most actual key's value are stored, therefore there is no need to check
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 95 When a device wants to signal the processor that there is some work to be done
139 an ISR. As such there are two commonly used methods for handling the
721 On an MMU system there should be no physical guards; the privilege mode stack
775 running in supervisor mode. If the thread drops to user mode, there is no guard
825 In addition to implementing these APIs, there are some other tasks as well:
952 GDB supports this by default and there is usually no need to
961 there is no need to implement these in architecture code.
983 of a memory region. Use ``0`` if there is no alignment requirement
|
| /Zephyr-latest/doc/services/logging/ |
| D | index.rst | 317 message (if pending), and returns true if there are more messages pending.
369 When enabled, logging manages the output so there is no interleaving. However,
474 for given entry since it indicates if there is at least one backend expecting
568 Since in all instances there is a standard logging subsystem, it is always possible
642 * If domains have the same timestamp source or if there is an out-of-bound mechanism that
643 recalculates timestamps, there are 2 options:
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | index.rst | 173 Depending on configuration, there are several constraints that must be
277 When enabled (see :kconfig:option:`CONFIG_NUM_METAIRQ_PRIORITIES`), there is a special
478 still used, but there are additional constraints which must be met or the
541 timer. For some architectures, SoCs or boards, there are timers with higher
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | lwm2m.rst | 571 Occurs if there is a timeout or failure in bootstrap registration.
591 … Occurs if there is socket errors or message timeouts. Client have lost connection to the server.
599 Occurs if there is a timeout or failure in the deregistration.
680 In LwM2M engine, there are three Kconfig options and one runtime value that configures how often the
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | float.rst | 156 register context, there are no provision for saving an ISR's FPU context
206 register context, there are no provision for saving an ISR's FPU context
298 when there is no need to do so.
|
12345678910>>...17
