Searched refs:linked (Results 76 – 100 of 122) sorted by relevance
12345
| /Zephyr-latest/doc/kernel/services/scheduling/ |
| D | index.rst | 62 * Simple linked-list ready queue (:kconfig:option:`CONFIG_SCHED_DUMB`)
115 * Simple linked-list wait_q (:kconfig:option:`CONFIG_WAITQ_DUMB`)
117 When selected, the wait_q will be implemented with a doubly-linked list.
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | slabs.rst | 61 The memory slab keeps track of unallocated blocks using a linked list;
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | lifos.rst | 23 The queue is implemented as a simple linked list.
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | x86.rst | 30 address space. Code and data are linked in virtual address space,
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 60 externally linked shared libraries. Which is to say: only static
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | eth_bridge_native_sim_setup.rst | 80 Ethernet interfaces which are linked to interfaces ``zeth0`` and ``zeth1`` in the host side.
|
| /Zephyr-latest/share/sysbuild/images/bootloader/ |
| D | Kconfig | 102 from there. The image must be linked to execute from RAM, the address that it is copied
|
| /Zephyr-latest/doc/contribute/ |
| D | external.rst | 18 compiled and linked into the final image, and programmed into the target
224 of the code compiled and linked into the final image. "Inclusion" in this
|
| D | bin_blobs.rst | 162 can be linked by a toolchain supported by the Zephyr Project. This is required
|
| /Zephyr-latest/doc/services/tfm/ |
| D | build.rst | 7 background, and linked with the Zephyr non-secure application. No knowledge
|
| /Zephyr-latest/boards/gaisler/gr716a_mini/doc/ |
| D | index.rst | 37 The application is linked to the on-chip tightly coupled memory by
|
| /Zephyr-latest/doc/develop/west/ |
| D | zephyr-cmds.rst | 121 CMake build targets, build targets that are linked together, and
|
| /Zephyr-latest/doc/introduction/ |
| D | index.rst | 87 * Simple linked-list ready queue
|
| /Zephyr-latest/doc/services/llext/ |
| D | build.rst | 114 Before the extension code is linked, if the architecture uses dynamic
|
| /Zephyr-latest/subsys/net/l2/openthread/ |
| D | Kconfig | 211 linked with OpenThread. Separate multiple values with space " ".
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.vm | 122 is linked and the implementation of an eviction algorithm and a
|
| D | Kconfig | 309 bool "Simple linked-list ready queue"
374 bool "Simple linked-list wait_q"
377 doubly-linked list. Choose this if you expect to have only
|
| /Zephyr-latest/soc/intel/intel_adsp/cavs/include/ |
| D | xtensa-cavs-linker.ld | 374 * sections need to be linked in safe/uncached memory but common-rom
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_l2.rst | 22 Only the L2 layer can talk to the device driver, linked to the net_if
|
| /Zephyr-latest/doc/ |
| D | glossary.rst | 32 fully-linked binary.
|
| /Zephyr-latest/soc/intel/intel_adsp/ace/ |
| D | ace-link.ld | 442 * sections need to be linked in safe/uncached memory but common-rom
|
| /Zephyr-latest/modules/ |
| D | Kconfig.mcuboot | 193 from there. The image must be linked to execute from RAM, the address that it is copied
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.5.rst | 233 * ``ZEP-555`` - correct libgcc not getting linked for CONFIG_FLOAT=y on ARM
|
| D | release-notes-1.11.rst | 344 * :github:`5351` - Some libraries should automatically be linked with 'app'
392 * :github:`5651` - [In Progress] arch: arm: linkder: vt must be linked at address 0x00000000 for Co…
|
| D | release-notes-1.8.rst | 123 * Host: GATT database changed to a linked list in preparation for dynamic allocation
|
12345
