Searched +full:- +full:- +full:directory (Results 1 – 25 of 613) sorted by relevance
12345678910>>...25
/Zephyr-latest/scripts/build/ |
D | subfolder_list.py | 2 # SPDX-License-Identifier: Apache-2.0 6 This script will walk the specified directory and write the file specified with 7 the list of all sub-directories found. If the output file already exists, the 8 file will only be updated in case sub-directories have been added or removed 24 parser.add_argument('-d', '--directory', required=True, 25 help='Directory to walk for sub-directory discovery') 26 parser.add_argument('-c', '--create-links', required=False, 27 help='Create links for each directory found in \ 28 directory given') 29 parser.add_argument('-o', '--out-file', required=True, [all …]
|
/Zephyr-latest/subsys/bluetooth/services/ots/ |
D | ots_dir_list_internal.h | 2 * Copyright (c) 2021 - 2022 Nordic Semiconductor ASA 4 * SPDX-License-Identifier: Apache-2.0 19 /** Maximum size of the Directory Listing Object Record. Table 4.1 in the OTS spec. */ 24 /** @brief Directory Listing Buffer Size 41 /** @brief Directory Listing record flag field. */ 49 /** Bit 3 Object First-Created Present*/ 51 /** Bit 4 Object Last-Modified Present*/ 63 * @param flags Directory Listing Object flags. 70 * @param flags Directory Listing Object flags. 77 * @param flags Directory Listing Object flags. [all …]
|
D | Kconfig | 3 # Copyright (c) 2020-2022 Nordic Semiconductor ASA 4 # SPDX-License-Identifier: Apache-2.0 18 bool "The Directory Listing Object" 20 Enables the Directory Listing Object, which is an object that contains all the metadata 25 string "The object name of the Directory Listing Object" 26 default "Directory" 29 The name of the Directory Listing Object when it is read by a client. 87 # Given the maximum size of a directory listing record (172) and the maximum size of an 88 # object using the net_buf implementation is 2^16-1, the maximum number of objects is given 89 # by 2^16-1 / 172 = 381 == 0x17D) [all …]
|
/Zephyr-latest/include/zephyr/fs/ |
D | fs_sys.h | 4 * SPDX-License-Identifier: Apache-2.0 97 * @name Directory operations 101 * Opens an existing directory specified by the path. 103 * @param dirp Directory to open. 104 * @param fs_path Path to the directory. 109 * Reads directory entries of an open directory. 111 * @param dirp Directory to read from. 112 * @param entry Next directory entry in the dirp directory. 117 * Closes an open directory. 119 * @param dirp Directory to close. [all …]
|
D | fs.h | 3 * Copyright (c) 2020-2024 Nordic Semiconductor ASA 5 * SPDX-License-Identifier: Apache-2.0 31 * @brief Enumeration for directory entry types 36 /** Identifier for directory entry */ 42 * Zephyr supports in-tree file systems and external ones. Each 46 * in-tree file systems. 55 /** Identifier for in-tree FatFS file system. */ 58 /** Identifier for in-tree LittleFS file system. */ 61 /** Identifier for in-tree Ext2 file system. */ 70 /** Flag makes mounted file system read-only */ [all …]
|
/Zephyr-latest/scripts/west_commands/ |
D | build_helpers.py | 3 # SPDX-License-Identifier: Apache-2.0 21 # Domains.py must be imported from the pylib directory, since 28 '''Name of the default Zephyr build directory.''' 34 If the build directory is not given, the default is {}/ unless the 35 build.dir-fmt configuration variable is set. The current directory is 36 checked after that. If either is a Zephyr build directory, it is used. 57 # Guess the build folder by iterating through all sub-folders from the 72 # Missing key, check sub-folders and match if a single one exists 85 '''Heuristic for finding a build directory. 87 The default build directory is computed by reading the build.dir-fmt [all …]
|
D | spdx.py | 3 # SPDX-License-Identifier: Apache-2.0 13 This command creates an SPDX 2.2 tag-value bill of materials 17 BUILDDIR/.cmake/api/v1/query/codemodel-v2 in order to enable 18 the CMake file-based API, which the SPDX command relies upon. 19 This can be done by calling `west spdx --init` prior to 35 # doc/guides/west/zephyr-cmds.rst up to date. 36 parser.add_argument('-i', '--init', action="store_true", 37 help="initialize CMake file-based API") 38 parser.add_argument('-d', '--build-dir', 39 help="build directory") [all …]
|
D | build.py | 3 # SPDX-License-Identifier: Apache-2.0 22 _ARG_SEPARATOR = '--' 30 west build [-h] [-b BOARD[@REV]]] [-d BUILD_DIR] 31 [-S SNIPPET] [--shield SHIELD] 32 [-t TARGET] [-p {auto, always, never}] [-c] [--cmake-only] 33 [-n] [-o BUILD_OPT] [-f] 34 [--sysbuild | --no-sysbuild] [--domain DOMAIN] 35 [--extra-conf FILE.conf] 36 [--extra-dtc-overlay FILE.overlay] 37 [source_dir] -- [cmake_opt [cmake_opt ...]] [all …]
|
/Zephyr-latest/cmake/modules/ |
D | user_cache.cmake | 1 # SPDX-License-Identifier: Apache-2.0 5 # Configure user cache directory. 11 # Only data that can be safely re-generated should be placed in this cache. 15 # See https://github.com/zephyrproject-rtos/zephyr/pull/7102 for details. 20 # - USER_CACHE_DIR: User cache directory in use. 26 # use only and may be removed, renamed, or re-purposed without prior notice. 36 # On macOS, ~/Library/Caches is the preferred cache directory. 69 # The directory is write-able 73 # The directory was not writeable, keep looking for a suitable 74 # directory [all …]
|
D | arch_v1.cmake | 1 # SPDX-License-Identifier: Apache-2.0 9 # Configure ARCH settings based on board directory and arch root. 12 # on board directory and arch root. 19 # - ARCH: Name of the arch in use. 20 # - ARCH_DIR: Directory containing the arch implementation. 21 # - ARCH_ROOT: ARCH_ROOT with ZEPHYR_BASE appended 24 # - ARCH_ROOT: CMake list of arch roots containing arch implementations 25 # - BOARD_DIR: CMake variable specifying the directory of the selected BOARD 28 # use only and may be removed, renamed, or re-purposed without prior notice.
|
/Zephyr-latest/include/zephyr/arch/posix/ |
D | linker.ld | 5 * SPDX-License-Identifier: Apache-2.0 17 #include <zephyr/linker/linker-defs.h> 18 #include <zephyr/linker/linker-tool.h> 25 #include <zephyr/linker/llext-sections.ld> 30 /* Located in generated directory. This file is populated by the 33 #include <snippets-rom-start.ld> 36 #include <zephyr/linker/common-rom.ld> 37 /* Located in generated directory. This file is populated by calling 40 #include <snippets-rom-sections.ld> 44 /* Located in generated directory. This file is populated by the [all …]
|
/Zephyr-latest/tests/posix/fs/src/ |
D | test_fs_dir.c | 4 * SPDX-License-Identifier: Apache-2.0 83 return -EIO; in test_lsdir() 90 if (entry->d_name[0] == 0) { in test_lsdir() 91 res = -EIO; in test_lsdir() 95 TC_PRINT("[FILE] %s\n", entry->d_name); in test_lsdir() 99 res = -EIO; in test_lsdir() 123 * @details Test creates a new directory through POSIX 124 * mkdir API and open a new file under the directory and 136 * @details Test opens an existing directory through POSIX 137 * opendir API, reads the contents of the directory through [all …]
|
/Zephyr-latest/doc/develop/west/ |
D | build-flash-debug.rst | 1 .. _west-build-flash-debug: 6 Zephyr provides several :ref:`west extension commands <west-extensions>` for 11 commands, see :ref:`flash-and-debug-support` in the board porting guide. 13 .. Add a per-page contents at the top of the page. This page is nested 21 .. _west-building: 26 .. tip:: Run ``west build -h`` for a quick overview. 29 use :ref:`west config <west-config-cmd>` to configure its behavior. 33 - If there is a Zephyr build directory named :file:`build` in your current 34 working directory, it is incrementally re-compiled. The same is true if you 35 run ``west build`` from a Zephyr build directory. [all …]
|
/Zephyr-latest/submanifests/ |
D | README.txt | 1 This directory can contain additional west manifest files. Any files 2 in this directory will be included in the main west.yml file sorted by 10 …hyrproject.org/latest/guides/west/manifest.html#example-2-2-downstream-with-directory-of-manifest-…
|
/Zephyr-latest/scripts/west_commands/zspdx/ |
D | sbom.py | 3 # SPDX-License-Identifier: Apache-2.0 23 # location of build directory 26 # location of SPDX document output directory 36 # create Cmake file-based API directories and query file 38 # 1) build_dir: build directory 40 # check that query dir exists as a directory, or else create it 44 log.err(f'cmake api query directory {cmakeApiDirPath} exists and is not a directory') 46 # directory exists, we're good 48 # create the directory 51 # check that codemodel-v2 exists as a file, or else create it [all …]
|
/Zephyr-latest/scripts/net/ |
D | README.txt | 1 The shell script run-sample-tests.sh runs selected Zephyr samples against 2 the network test applications Docker container provided by the 'net-tools' 3 Zephyr project, https://github.com/zephyrproject-rtos/net-tools. 10 'net-tools' Docker container has been created, see the first bullet point 11 at the net-tools Docker README file 12 https://github.com/zephyrproject-rtos/net-tools/blob/master/README.docker. 17 * Check out the net-tools project from github or update it with west 18 * Change working directory to the net-tools repository 20 * Run 'docker build -t net-tools .' 22 This creates a Docker image called 'net-tools' which the script will need as [all …]
|
/Zephyr-latest/subsys/fs/ext2/ |
D | ext2_impl.h | 4 * SPDX-License-Identifier: Apache-2.0 68 * @retval -EINVAL when superblock of ext2 was not detected 69 * @retval -ENOTSUP when described file system is not supported 79 * @retval -EROFS when superblock is not valid but file system may be mounted read only 80 * @retval -EINVAL when superblock is not valid and file system cannot be mounted at all 81 * @retval -ENOTSUP when superblock has some field set to value that we don't support 117 * @retval -ENOSPC when storage device is too small for ext2 file system 118 * @retval -ENOTSUP when storage device is too big (file systems with more than 132 * - path 133 * - flags [all …]
|
/Zephyr-latest/scripts/tests/twister/ |
D | README.md | 5 …located in $ZEPHYR_BASE/scripts/tests directory with all the data files in $ZEPHYR_BASE/scripts/te… 12 pip install -r $ZEPHYR_BASE/scripts/requirements-build-test.txt 17 The testcases can be executed from the root directory using 28 coverage run -m pytest $ZEPHYR_BASE/scripts/tests/twister/ 34 coverage report -m $ZEPHYR_BASE/scripts/pylib/twister/ 40 coverage report -m $ZEPHYR_BASE/scripts/twister 49 …rage html report can be generated in every run of "pytest" in the tests directory using configurat… 53 - conftest.py: Contains common fixtures for use in testing the twister tool. 54 - test_twister.py : Contains basic testcases for environment variables, verifying testcase & platfo… 55 - test_testsuite_class.py : Contains testcases for Testsuite class (except reporting functionality)… [all …]
|
/Zephyr-latest/ |
D | .gitignore | 24 # The .cache directory will be used to cache toolchain capabilities if 25 # no suitable out-of-tree directory is found. 29 outdir-* 32 coverage-report 33 doc-coverage.info 41 doc/themes/zephyr-docs-theme 42 sanity-out* 43 twister-out* 55 hide-defaults-note 69 # Normal west builds will place the Rust target directory under the build directory. However,
|
/Zephyr-latest/doc/hardware/arch/ |
D | x86.rst | 10 x86-based platforms. 29 On 32-bit x86, it is possible to have separate physical and virtual 38 at the page directory level, in addition to mapping virtual addresses 40 the entries for identity mapping at the page directory level are 45 is done at the page directory level, there is no need to allocate 47 still be required for additional page directory table. 51 - Physical and virtual address spaces must be disjoint. This is 52 required as the entries in page directory table will be cleared. 56 - If :kconfig:option:`CONFIG_X86_PAE` is enabled (``=y``), each address space 58 (Page Directory Pointer) covers 1GB of memory. For example: [all …]
|
/Zephyr-latest/tests/net/all/ |
D | check_net_options.sh | 5 # SPDX-License-Identifier: Apache-2.0 7 if [ -z "$1" ]; then 8 echo "Usage: $0 <doc build directory>" 10 echo "The parameter needs to point to a directory where Zephyr html" 21 if [ ! -d $build_dir ]; then 22 echo "Directory $build_dir not found!" 28 if [ ! -d $kconfig_dir ]; then 40 grep -q $opt prj.conf > /dev/null 2>&1 41 if [ $? -ne 0 ]; then 46 echo "Total number of options : `get_options | wc -w`" > /dev/tty
|
/Zephyr-latest/include/zephyr/arch/sparc/ |
D | linker.ld | 2 * Copyright (c) 2019-2020 Cobham Gaisler AB 4 * SPDX-License-Identifier: Apache-2.0 16 #include <zephyr/linker/linker-defs.h> 17 #include <zephyr/linker/linker-tool.h> 24 #include <zephyr/linker/rel-sections.ld> 27 #include <zephyr/linker/llext-sections.ld> 48 #include <zephyr/linker/common-rom.ld> 49 /* Located in generated directory. This file is populated by calling 52 #include <snippets-rom-sections.ld> 53 #include <zephyr/linker/thread-local-storage.ld> [all …]
|
/Zephyr-latest/cmake/ |
D | vif.cmake | 2 # SPDX-License-Identifier: Apache-2.0 4 # Generates USB-C VIF policies in XML format from device tree. 6 set(dts_compatible usb-c-connector) 12 --edt-pickle ${EDT_PICKLE} 13 --compatible ${dts_compatible} 14 --vif-out ${vif_out} 36 list(APPEND cmd_gen_vif --vif-source-xml ${vif_source_xml}) 43 " '${board_vif_xml}' in 'boards' directory of application" 44 " directory, or create '${vif_xml}' file in application" 45 " directory or board directory, or supply a custom XML VIF path"
|
/Zephyr-latest/samples/subsys/shell/fs/ |
D | README.rst | 1 .. zephyr:code-sample:: shell-fs 3 :relevant-api: file_system_api 25 .. zephyr-app-commands:: 26 :zephyr-app: samples/subsys/shell/fs 32 :file:`flash.bin`, in the current directory to keep the flash content. 35 .. code-block:: console 37 zephyr/zephyr.exe -help 43 --------------------------------------- 48 Before starting a build, make sure that the i386 pkgconfig directory is in your 49 search path and that a 32-bit version of libfuse is installed. For more [all …]
|
/Zephyr-latest/doc/develop/application/ |
D | index.rst | 10 …- your **application directory**, :file:`<app>`, is something like :file:`<home>/zephyrproject/app` 11 - its **build directory** is :file:`<app>/build` 19 <important-build-vars>` is set appropriately, though.) 26 The build system is application-centric, and requires Zephyr-based applications 36 The files in the **application directory** link Zephyr and any modules with the 37 application. This directory contains all application-specific files, such as 38 application-specific configuration files and source code. 42 .. code-block:: none 55 application files, and links the application directory with Zephyr's CMake 57 such as board-specific configuration files, the ability to run and [all …]
|
12345678910>>...25