Searched refs:reasons (Results 1 – 25 of 42) sorted by relevance
12
| /Zephyr-latest/modules/littlefs/ |
| D | Kconfig | 8 # reasons.
|
| /Zephyr-latest/modules/fatfs/ |
| D | Kconfig | 8 # reasons.
|
| /Zephyr-latest/soc/st/stm32/stm32wb0x/ |
| D | ram_sections.ld | 10 /* For historical reasons, leave the first word of
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 003_rfc-proposal.md | 58 List any alternatives considered, and the reasons for choosing this option
|
| /Zephyr-latest/doc/services/storage/stream/ |
| D | stream_flash.rst | 14 There are several reasons why one might want to use buffered writes instead of
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.mem_domain | 51 For these reasons, on uniprocessor systems unless memory access
|
| /Zephyr-latest/dts/arm/nxp/ |
| D | nxp_lpc11u6x.dtsi | 47 * For some reasons, the IAP commands don't allow to
|
| /Zephyr-latest/doc/project/ |
| D | proposals.rst | 83 If built properly, the roadmap can be a valuable tool for several reasons. It
|
| /Zephyr-latest/doc/services/pm/ |
| D | power_domain.rst | 70 Placing devices on power domains can be done for a variety of reasons,
|
| /Zephyr-latest/doc/develop/west/ |
| D | why.rst | 70 In this context, there are a few reasons to work with multiple Git
|
| /Zephyr-latest/ |
| D | CODE_OF_CONDUCT.md | 48 not aligned to this Code of Conduct, and will communicate reasons for moderation
|
| /Zephyr-latest/lib/os/ |
| D | Kconfig.cbprintf | 111 Picolibc does not support this feature for security reasons.
|
| /Zephyr-latest/samples/kernel/metairq_dispatch/ |
| D | README.rst | 57 and working log output. For precision reasons, it produces better
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 56 architectures to define their own for performance reasons.
111 available for convenience. For obvious reasons, these APIs are
259 for these reasons they are disabled by default. The first is a cost incurred
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 97 This style is accepted for historical reasons: Kconfig configuration files
281 type once at the "base" definition of the symbol is a good idea for reasons
|
| /Zephyr-latest/boards/snps/nsim/arc_v/doc/ |
| D | index.rst | 143 reasons for that. ``.tcf`` perfectly suits building of bare-metal single-thread application -
|
| /Zephyr-latest/cmake/modules/ |
| D | kernel.cmake | 155 # but for legacy reasons we need it to be set to
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 159 - For performance and footprint reasons Zephyr normally does little or no
|
| D | kernelobjects.rst | 141 supervisor threads are still tracked for two reasons:
|
| /Zephyr-latest/doc/kernel/services/ |
| D | polling.rst | 86 reasons. If using runtime initializers, the user must set it separately in the
|
| /Zephyr-latest/doc/develop/test/ |
| D | pytest.rst | 310 hardwares). If anyone is interested in doing this for some reasons (for example via
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net_config_guide.rst | 46 there is some overhead involved for each net_buf. For these reasons the default
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 120 reasons on a case by case basis (see library-specific requirements below).
|
| /Zephyr-latest/boards/snps/nsim/arc_classic/doc/ |
| D | index.rst | 279 reasons for that. ``.tcf`` perfectly suits building of bare-metal single-thread application -
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro-syntax-structure.rst | 314 properties continue to persist for historical reasons in some existing
|
12
