Searched refs:needs (Results 201 – 225 of 523) sorted by relevance
12345678910>>...21
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 12 No special application code needs to be written to take advantage of
146 many architectures the timer is a per-CPU device and needs to be
166 case that state modified on the local CPU needs to be synchronously
280 needs to reflect what is running locally, there are many threads
282 needs to be created and assigned for each physical CPU, as does the
320 Instead, the SMP "switch to" decision needs to be made synchronously
|
| /Zephyr-latest/cmake/compiler/iar/ |
| D | target.cmake | 98 # IAR needs Dwarf 4 output
|
| /Zephyr-latest/boards/rakwireless/rak4631/doc/ |
| D | index.rst | 60 and Documentation pack for Linux". The application JLinkExe needs to be
|
| /Zephyr-latest/arch/common/ |
| D | Kconfig | 51 As a result of this, both respective MPUs needs to fully partition the
|
| /Zephyr-latest/doc/services/crypto/random/ |
| D | index.rst | 23 The CTR-DRBG generator needs an entropy source to establish and
|
| /Zephyr-latest/samples/net/sockets/echo_server/ |
| D | Kconfig | 12 Each connection is served by a thread which needs
|
| /Zephyr-latest/drivers/ethernet/phy/ |
| D | Kconfig | 27 Note that the priority needs to be lower than the net stack
|
| /Zephyr-latest/subsys/net/lib/capture/ |
| D | Kconfig | 46 if one needs to send captured data to multiple different devices,
|
| /Zephyr-latest/doc/services/storage/nvs/ |
| D | nvs.rst | 64 device needs to be operational.
85 needs to be restored after reboot. NVS has been defined with a sector_size
|
| /Zephyr-latest/drivers/net/ |
| D | Kconfig | 75 This enables PPP packet capture. One needs to configure the
238 The priority needs to be lower than the network stack and higher than the CAN controller
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 129 It thus needs an architecture-specific implementation, called the
320 stack. Refer to the toolchain documentation on how the storage area needs
475 Each architecture also needs its own linker script, even if most sections can
484 their I/O regions, :kconfig:option:`CONFIG_MMU` needs to be enabled and the
827 * :c:func:`_new_thread` needs to spawn threads with :c:macro:`K_USER` in
836 * On context switch, the system needs to switch between memory domains for
844 * A software interrupt or some kind of privilege elevation mechanism needs to
846 are implemented. On system call, the appropriate handler function needs to
862 store the GDB exception reason. This value needs to be set before
868 * Pointer to this struct needs to be passed to :c:func:`z_gdb_main_loop`,
[all …]
|
| /Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/ |
| D | README.rst | 32 host, the device can tell host how many samples on average it needs every frame.
|
| /Zephyr-latest/samples/tfm_integration/psa_protected_storage/ |
| D | README.rst | 37 Note that the board needs to be completely erased before programming the sample, as the flash area
|
| /Zephyr-latest/boards/adafruit/macropad_rp2040/ |
| D | adafruit_macropad_rp2040.dts | 196 ready-time-ms = <100>; /* SH1106G needs 100ms delay after init */
|
| /Zephyr-latest/doc/hardware/peripherals/edac/ |
| D | ibecc.rst | 71 Exceptional care needs to be taken with Non Maskable Interrupt (NMI). NMI will
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig | 98 Note that the priority needs to be lower than the net stack
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 293 process needs to be authenticated first. Mechanisms to store
340 option and needs to be explicitly enabled. Then, all features,
431 purposes the integrity of the release needs to be ensured in a
437 needs to be ensured by an appropriate rights management (e.g.,
450 needs to be clearly defined and its application needs to be monitored
454 known and future attack vectors, and their impact on the system needs to
622 certification scheme and evaluation level, this process needs to be
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | memory_domain.rst | 44 memory it needs, and regions are defined which grant user mode access to
128 - :c:func:`k_poll` when invoked from user mode, needs to make a kernel-side
189 the underlying memory management hardware, and needs to conform to any
357 /* the start address of the MPU region needs to align with its size */
379 /* the start address of the MPU region needs to align with its size */
|
| /Zephyr-latest/subsys/net/lib/http/ |
| D | Kconfig | 107 internal header processing, and only needs to be increased if the
118 and only needs to be increased if the application wishes to send
|
| /Zephyr-latest/doc/introduction/ |
| D | index.rst | 94 Allows an application to incorporate *only* the capabilities it needs as it
95 needs them, and to specify their quantity and size.
|
| /Zephyr-latest/scripts/net/ |
| D | README.txt | 14 In essence, the following needs to be done:
|
| /Zephyr-latest/boards/rakwireless/rak5010/doc/ |
| D | index.rst | 68 and Documentation pack for Linux". The application JLinkExe needs to be
|
| /Zephyr-latest/doc/build/dts/ |
| D | design.rst | 81 dtschema does not yet meet Zephyr's needs, we should try to follow what it is
|
| /Zephyr-latest/boards/up-bridge-the-gap/up_squared/doc/ |
| D | index.rst | 35 GPIO, there is an option to set the direction of the pin. This needs
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.ublox-sara-r4 | 90 Note that the priority needs to be lower than the net stack
|
12345678910>>...21
