Home
last modified time | relevance | path

Searched full:edk (Results 1 – 19 of 19) sorted by relevance

/Zephyr-latest/samples/subsys/llext/edk/
DREADME.rst1 .. zephyr:code-sample:: llext-edk
2 :name: Linkable loadable extensions EDK
6 LLEXT EDK (Extension Development Kit).
11 This sample demonstrates how to use the Zephyr LLEXT EDK (Extension Development
29 Note that the kernel extension is only available when the EDK is built with
33 The application is built using the Zephyr build system. The EDK is built using
34 the Zephyr build system as well, via ``llext-edk`` target. The EDK is then
38 during build time, which is not really practical. This sample is about the EDK
41 Zephyr application - even on different machines, using only the EDK. At the
43 different teams, using the EDK provided by the application developer.
[all …]
/Zephyr-latest/samples/subsys/llext/edk/app/
Dsample.yaml4 - edk
9 description: EDK sample application
10 name: EDK sample application
12 sample.edk.app:
15 - edk
/Zephyr-latest/tests/misc/llext-edk/pytest/
Dtest_edk.py19 # otherwise can't actually build the edk
24 # Can we build the edk?
31 "llext-edk",
38 # Install the edk to a temporary location
40 # Copy the edk to the temporary directory using python methods
41 logger.debug(f"Copying llext-edk.tar.xz to {tempdir}")
42 edk_path = Path(unlaunched_dut.device_config.build_dir) / "zephyr/llext-edk.tar.xz"
45 # Extract the edk using tar
46 logger.debug(f"Extracting llext-edk.tar.xz to {tempdir}")
47 command = ["tar", "-xf", "llext-edk.tar.xz"]
[all …]
/Zephyr-latest/subsys/llext/
DKconfig110 menu "Linkable loadable Extension Development Kit (EDK)"
113 string "Name for llext EDK (Extension Development Kit)"
114 default "llext-edk"
116 Name will be used when generating the EDK file, as <name>.tar.xz.
118 stating EDK location, used on generated Makefile.cflags. For
119 instance, the default name, "llext-edk", becomes LLEXT_EDK_INSTALL_DIR.
122 bool "Only generate the Userpace codepath on syscall stubs for the EDK"
125 or kernel space and route the call accordingly. If the EDK is expected
126 to be used by userspace only extensions, this option will make EDK stubs
/Zephyr-latest/doc/services/llext/
Dbuild.rst133 LLEXT Extension Development Kit (EDK)
143 (EDK) from the build artifacts of the main Zephyr application, by running the
144 following command which uses the ``llext-edk`` target:
148 west build -t llext-edk
150 The generated EDK can be found in the build directory under the ``zephyr``
158 The EDK includes the convenience files ``cmake.cflags`` (for CMake-based
199 LLEXT EDK Kconfig options argument
202 The LLEXT EDK can be configured using the following Kconfig options:
205 The name of the generated EDK tarball.
208 If set, the EDK will include headers that do not contain code to route
[all …]
Dconfig.rst118 This option is not currently compatible with the :ref:`LLEXT EDK
129 EDK configuration
132 Options influencing the generation and behavior of the LLEXT EDK are described
/Zephyr-latest/tests/misc/llext-edk/
Dtestcase.yaml2 misc.edk.pytest:
6 - edk
/Zephyr-latest/cmake/usage/
Dusage.cmake37 message(" llext-edk - Build the Linkable Loadable Extension (LLEXT) Extension Development Kit (…
/Zephyr-latest/cmake/
Dllext-edk.cmake27 # edk directory. This is necessary when building an extension that only
28 # supports userspace, as the syscall headers are regenerated in the edk
35 "The LLEXT EDK is not compatible with CONFIG_LLEXT_EXPORT_BUILTINS_BY_SLID.")
151 # Copy syscall headers from edk directory, as they were regenerated there.
152 …file(COPY ${PROJECT_BINARY_DIR}/edk/include/generated/ DESTINATION ${llext_edk_inc}/zephyr/include…
/Zephyr-latest/samples/subsys/llext/edk/ext2/
DCMakeLists.txt11 # Include EDK CFLAGS
/Zephyr-latest/samples/subsys/llext/edk/ext1/
DCMakeLists.txt11 # Include EDK CFLAGS
/Zephyr-latest/samples/subsys/llext/edk/ext3/
DCMakeLists.txt11 # Include EDK CFLAGS
/Zephyr-latest/samples/subsys/llext/edk/k-ext1/
DCMakeLists.txt11 # Include EDK CFLAGS
/Zephyr-latest/samples/subsys/llext/edk/app/src/
Dmain.c18 * EDK. If others are not built, this will just fail.
24 # pragma message "Extension 1 not built, assuming EDK build."
/Zephyr-latest/boards/qemu/x86/doc/
Dindex.rst146 EDK II
147 UEFI v2.70 (EDK II, 0x00010000)
/Zephyr-latest/
DCMakeLists.txt684 set(edk_syscall_list_h ${CMAKE_CURRENT_BINARY_DIR}/edk/include/generated/zephyr/syscall_list.h)
2223 # Extension Development Kit (EDK) generation.
2243 -E make_directory edk/include/generated/zephyr
2248 --base-output edk/include/generated/zephyr/syscalls # Write to this dir
2249 --syscall-dispatch edk/include/generated/zephyr/syscall_dispatch.c # Write this file
2264 -P ${ZEPHYR_BASE}/cmake/llext-edk.cmake
2268 add_custom_target(llext-edk DEPENDS ${llext_edk_file})
DMAINTAINERS.yml5542 - cmake/llext-edk.cmake
D.ruff-excludes.toml1785 "./tests/misc/llext-edk/pytest/test_edk.py",
/Zephyr-latest/doc/releases/
Drelease-notes-3.7.rst31 * A new :ref:`LLEXT Extension Developer Kit (EDK) <llext_build_edk>` makes it easier to develop and