Home
last modified time | relevance | path

Searched refs:early (Results 26 – 50 of 57) sorted by relevance

123

/Zephyr-latest/doc/kernel/usermode/
Dkernelobjects.rst210 is run by the kernel early in the boot process.
/Zephyr-latest/doc/contribute/
Dexternal.rst193 early submission process to the Zephyr governing board for further review
Dcontributor_expectations.rst105 provide early feedback, even with failing CI checks.
Dguidelines.rst946 #. Watch early CI results immediately after submissions and fix issues as they
/Zephyr-latest/arch/x86/
DKconfig296 bool "Support very early boot printk"
/Zephyr-latest/subsys/debug/
DKconfig242 This option will enable stdout as early as possible, for debugging
/Zephyr-latest/doc/services/logging/
Dcs_stm.rst56 STMESP cannot be used before STM or ETR/TPIU is setup. In order to support early logging,
/Zephyr-latest/doc/hardware/porting/
Darch.rst23 * **The early boot sequence**: each architecture has different steps it must
63 The goal of the early boot sequence is to take the system from the state it is
74 * Jump to :code:`z_cstart()`, the early kernel initialization
/Zephyr-latest/doc/develop/tools/
Dcoccinelle.rst152 a few threads. With dynamic load balancing, if a thread finishes early we keep
/Zephyr-latest/doc/hardware/pinctrl/
Dindex.rst180 de-initialization yet, this functionality should only be used during early
/Zephyr-latest/boards/native/doc/
Darch_soc.rst23 target hardware in the early phases of development.
/Zephyr-latest/doc/releases/
Drelease-notes-1.12.rst49 * kernel: handle early entropy issues
440 * :github:`6577` - sam0: SPI CS released too early
Drelease-notes-2.5.rst222 architecture state during early system boot (Cortex-M).
907 application during its early initialization.
1775 * :github:`26912` - arm: cortex_r: config_userspace: hang during early power-up
1950 * :github:`7404` - arch: arm: MSP initialization during early boot
Drelease-notes-2.6.rst199 * Added support for clearing NXP MPU region configuration during Zephyr early boot stage.
276 * Changed the pairing procedure to fail early if the remote device could not
1864 * :github:`32771` - STM32 with Ethernet crashes when receiving packets early
2078 * :github:`28803` - Use generic config option for early platfrom init (AKA "warm boot")
Drelease-notes-2.4.rst724 * Very early support for Periodic Advertising. This should be considered an
725 early experimental draft at this stage.
1421 * :github:`26271` - k_sleep/k_msleep ends too early on UP_squared board
Dmigration-guide-3.7.rst319 furthermore allows CAN controller drivers not supporting manual recovery mode to fail early in
Drelease-notes-2.0.rst776 * :github:`17809` - Bluetooth Mesh message cached too early when LPN
1400 * :github:`11626` - k_busy_wait exits early on Nordic chips
Drelease-notes-1.13.rst578 * :github:`8128` - scheduler: threads using k_sleep can be _swap()'d back too early
Drelease-notes-2.2.rst871 * :github:`22356` - An application hook for early init
Drelease-notes-3.0.rst475 to fail early in :c:func:`can_send` if in :c:macro:`CAN_STATE_BUS_OFF`.
/Zephyr-latest/doc/connectivity/networking/api/
Dlwm2m.rst701 :alt: LwM2M seconds to update early
/Zephyr-latest/subsys/net/ip/
DKconfig158 early in the boot the network stack is initialized.
/Zephyr-latest/doc/hardware/arch/
Darm_cortex_m.rst119 The interrupt stack is also used during early boot so the kernel can initialize the main thread's s…
/Zephyr-latest/
DKconfig.zephyr36 # This should be early since the autogen Kconfig.dts symbols may get
/Zephyr-latest/doc/develop/application/
Dindex.rst663 are still in early stages of their development cycle. Such features will be

123