Searched refs:overlap (Results 1 – 24 of 24) sorted by relevance
/Zephyr-Core-3.5.0/scripts/build/ |
D | mergehex.py | 16 def merge_hex_files(output, input_hex_files, overlap): argument 28 ih.merge(to_merge, overlap=overlap) 52 merge_hex_files(args.output, args.input_files, args.overlap)
|
/Zephyr-Core-3.5.0/cmake/compiler/host-gcc/ |
D | compiler_flags.cmake | 2 # Significant overlap with freestanding gcc compiler so reuse it
|
/Zephyr-Core-3.5.0/samples/drivers/memc/ |
D | README.rst | 14 overlap with memory used for XIP or SRAM by the application, as the sample
|
/Zephyr-Core-3.5.0/include/zephyr/linker/ |
D | intlist.ld | 25 * shouldn't overlap any other regions. On most arches the following should be
|
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/ll/cis/ |
D | Kconfig | 55 scanning to overlap with advertising events hence do not use
|
/Zephyr-Core-3.5.0/include/zephyr/arch/x86/ |
D | memory.ld | 55 * Board-level DTS must specify a flash region that doesn't overlap with 104 * target. However, it shouldn't overlap any other regions.
|
/Zephyr-Core-3.5.0/drivers/display/ |
D | Kconfig.mcux_dcnano_lcdif | 47 does not overlap with other data. Each allocated LCDIF buffer will
|
/Zephyr-Core-3.5.0/arch/x86/zefi/ |
D | README.txt | 81 doesn't overlap with the target Zephyr memory. In practice on the 87 the overlap and warn about it.
|
/Zephyr-Core-3.5.0/include/zephyr/arch/arm64/scripts/ |
D | linker.ld | 146 * section overlap. 227 * than __rodata_region_end, and this two regions can overlap.
|
/Zephyr-Core-3.5.0/soc/arm64/nxp_imx/mimx9/ |
D | linker.ld | 146 * section overlap. 227 * than __rodata_region_end, and this two regions can overlap.
|
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/ |
D | overview.rst | 48 * Intelligent scheduling of roles to minimize overlap
|
/Zephyr-Core-3.5.0/include/zephyr/arch/arm/cortex_a_r/scripts/ |
D | linker.ld | 172 * section overlap.
|
/Zephyr-Core-3.5.0/arch/xtensa/core/ |
D | README-WINDOWS.rst | 107 caller-save. When using CALLn, you always need to overlap 4 registers
|
/Zephyr-Core-3.5.0/kernel/ |
D | Kconfig.vm | 91 there isn't overlap with the existed mappings, it will reserve the
|
/Zephyr-Core-3.5.0/include/zephyr/arch/arm/cortex_m/scripts/ |
D | linker.ld | 167 * section overlap.
|
/Zephyr-Core-3.5.0/doc/kernel/usermode/ |
D | memory_domain.rst | 180 - Partitions within the same memory domain may not overlap each other. There is 184 overlap a boot-time memory region is architecture specific.
|
/Zephyr-Core-3.5.0/boards/x86/acrn/doc/ |
D | index.rst | 180 configuring multiple guests, you probably don't want to overlap these
|
/Zephyr-Core-3.5.0/boards/x86/qemu_x86/ |
D | qemu_x86_tiny.ld | 72 * target. However, it shouldn't overlap any other regions.
|
/Zephyr-Core-3.5.0/boards/arm/mps2_an521/doc/ |
D | index.rst | 98 some overlap in the memory maps.
|
/Zephyr-Core-3.5.0/subsys/bluetooth/controller/ |
D | Kconfig.ll_sw_split | 458 bool "Skip Periodic Sync event on overlap with Extended Scan Event" 659 and/or PHY Update procedure to avoid overlap of radio events
|
/Zephyr-Core-3.5.0/doc/hardware/arch/ |
D | arm_cortex_m.rst | 513 overlap. :kconfig:option:`CONFIG_MPU_GAP_FILLING` controls whether the fixed MPU region
|
/Zephyr-Core-3.5.0/doc/releases/ |
D | release-notes-3.3.rst | 2653 - :github:`51024` - aarch32 excn vector not pinned in mmu causing newlib heap overlap 2802 - :github:`54577` - IPv6 defragmenting fails when segments do not overlap 2926 * :github:`54393` - Bluetooth: Controller: Starting a second BIG causes them to overlap and have tw… 2938 * :github:`54344` - Bluetooth: Controller: Central ACL connections overlap Broadcast ISO BIG event 3101 * :github:`53221` - Systemview trace id overlap
|
D | release-notes-2.4.rst | 1383 * :github:`26413` - disco_l475_iot1: flash storage corruption caused by partition overlap 1607 * :github:`24859` - os: Add memory partition overlap assert check is not made for x86 boards
|
D | release-notes-3.2.rst | 2049 * :github:`49036` - soc: telink_b91: ROM region section overlap
|