Searched refs:extensions (Results 1 – 25 of 102) sorted by relevance
12345
| /Zephyr-latest/samples/subsys/llext/edk/ |
| D | README.rst | 2 :name: Linkable loadable extensions EDK
13 extensions that it loads. The provided API is a simple publish/subscribe system,
14 based on :ref:`Zbus <zbus>`, which extensions use to communicate with each other.
17 published and republishes them via Zbus to the extensions that are
18 subscribers. There are four extensions, which are loaded by the application and
35 extracted and the extensions are built using CMake.
37 Finally, the way the application loads the extensions is by including them
39 providing the ability to build extensions independently from the application.
40 One could build the extensions in different directories, not related to the
42 limit, one could even imagine a scenario where the extensions are built by
[all …]
|
| /Zephyr-latest/cmake/modules/ |
| D | doc.cmake | 9 # - extensions
20 include(extensions)
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | risc-v.rst | 13 ISA extensions as well as :ref:`semihosting<semihost_guide>`.
22 ISA extensions
25 It's possible to set in Zephyr which ISA extensions (RV32/64I(E)MAFD(G)QC)
|
| /Zephyr-latest/soc/neorv32/ |
| D | Kconfig.soc | 10 extensions enabled in order to support Zephyr:
14 The following NEORV32 CPU ISA extensions are not currently supported
|
| /Zephyr-latest/tests/lib/devicetree/api_ext/ |
| D | README | 1 Test cases for the devicetree.h extensions (GPIO, SPI, etc).
|
| /Zephyr-latest/doc/develop/tools/ |
| D | vscode.rst | 7 and has a rich set of extensions.
20 Install the required extensions through the :guilabel:`Extensions` marketplace in the left panel.
73 There are many other extensions that can be useful when working with Zephyr and VS Code. While this
82 Documentation languages extensions
87 IDE extensions
102 …Please be aware that these extensions might not all have the same level of quality and maintenance.
|
| /Zephyr-latest/doc/ |
| D | conf.py | 72 extensions = [ variable
104 extensions.append("sphinxcontrib.rsvgconverter")
105 extensions.append("sphinx.ext.imgconverter")
|
| /Zephyr-latest/subsys/testsuite/boards/unit_testing/unit_testing/ |
| D | Kconfig.defconfig | 10 # Bluetooth unit tests assume HCI vendor extensions are available
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | debug-sections.ld | 20 /* GNU DWARF 1 extensions */
34 /* SGI/MIPS DWARF 2 extensions */
|
| /Zephyr-latest/doc/services/llext/ |
| D | build.rst | 1 Building extensions
4 The LLEXT subsystem allows for the creation of extensions that can be loaded
5 into a running Zephyr application. When building these extensions, it's very
28 extensions as part of the Zephyr application. This is the simplest way to build
29 extensions, as it requires minimal additions to an application build system.
136 When building extensions as a standalone project, outside of the main Zephyr
152 to build extensions. The extension developer can then include the headers
209 syscalls to the kernel. This is useful when building extensions that will
|
| D | config.rst | 29 The LLEXT subsystem supports loading different types of extensions; the type
98 main application to extensions. This table can then be searched into by the
106 extensions being built, converting every string in the symbol tables to
124 extensions is not supported. For example, if the main application
|
| /Zephyr-latest/share/sysbuild/cmake/modules/ |
| D | sysbuild_default.cmake | 8 include(extensions)
|
| /Zephyr-latest/samples/subsys/llext/shell_loader/ |
| D | README.rst | 2 :name: Linkable loadable extensions shell module
5 Manage loadable extensions using shell commands.
11 ability to manage loadable code extensions in the shell.
41 list :List loaded extensions and their size in memory
139 This extension can then be seen in the list of loaded extensions (``list``), its symbols printed
|
| /Zephyr-latest/doc/hardware/peripherals/audio/ |
| D | i2s.rst | 10 as well as common non-standard extensions such as PCM Short/Long Frame Sync
|
| /Zephyr-latest/subsys/llext/ |
| D | CMakeLists.txt | 22 message(WARNING "Running LLEXT extensions from user-space threads on RISC-V is not supported!")
|
| D | Kconfig | 5 bool "Linkable loadable extensions"
80 Select if LLEXT storage is writable, i.e. if extensions are stored in
126 to be used by userspace only extensions, this option will make EDK stubs
|
| /Zephyr-latest/subsys/modbus/ |
| D | Kconfig | 70 bool "Floating-Point extensions"
73 Enable Floating-Point extensions
|
| /Zephyr-latest/doc/_scripts/ |
| D | gen_boards_catalog.py | 19 def guess_file_from_patterns(directory, patterns, name, extensions): argument
21 for ext in extensions:
|
| /Zephyr-latest/cmake/linker_script/common/ |
| D | debug-sections.cmake | 21 # GNU DWARF 1 extensions
40 # SGI/MIPS DWARF 2 extensions
|
| /Zephyr-latest/doc/develop/west/ |
| D | extensions.rst | 1 .. _west-extensions:
7 source code. These are called **west extension commands**, or just "extensions"
15 :ref:`ones described here <west-zephyr-ext-cmds>` , are extensions. That's why
155 gives the location of a file implementing west extensions, along with the names
156 of those extensions, and optionally the names of the classes which define them
175 If you have multiple extensions, or want to split your extensions across
198 - :file:`another_file.py` defines two extensions:
|
| /Zephyr-latest/scripts/west_commands/ |
| D | README.txt | 6 extensions in upstream west. For example, any commands which operate
|
| /Zephyr-latest/cmake/toolchain/xcc/ |
| D | common.cmake | 45 list(APPEND TOOLCHAIN_C_FLAGS -fms-extensions)
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.xsi | 37 bool "X/Open threads extensions"
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | testsuite.py | 281 def find_c_files_in(path: str, extensions: list = None) -> list:
285 if extensions is None:
286 extensions = ['c', 'cpp', 'cxx', 'cc']
295 for ext in extensions:
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | index.rst | 31 extensions.rst
|
12345
