directory (full) in projects: OK3568_Linux_fs

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:directory (Results 1 – 25 of 5501) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...221

/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/s390/cf_z13/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/OK3568_Linux_fs/yocto/poky/documentation/ref-manual/
H A D	structure.rst	4 Source Directory Structure 7 The :term:`Source Directory` consists of numerous files, 10 describes the Source Directory and gives information about those files 13 For information on how to establish a local Source Directory on your 20 The OpenEmbedded build system does not support file or directory 21 names that contain spaces. Be sure that the Source Directory you use 29 This section describes the top-level components of the :term:`Source Directory`. 36 This directory includes a copy of BitBake for ease of use. The copy 44 resides in the ``bitbake/bin/`` directory) starts. Sourcing the 57 This directory contains user configuration files and the output [all …]
H A D	terms.rst	62 :term:`Build Directory` 65 script that is found in the Source Directory 67 :term:`TOPDIR` variable points to the Build Directory. 69 You have a lot of flexibility when creating the Build Directory. 70 Following are some examples that show how to create the directory. The 71 examples assume your :term:`Source Directory` is named ``poky``: 73 - Create the Build Directory inside your Source Directory and let 74 the name of the Build Directory default to ``build``: 81 - Create the Build Directory inside your home directory and 88 - Provide a directory path and specifically name the Build [all …]
/OK3568_Linux_fs/kernel/Documentation/filesystems/ext4/
H A D	directory.rst	3 Directory Entries 6 In an ext4 filesystem, a directory is more or less a flat file that maps 8 filesystem. There can be many directory entries across the filesystem 11 such, directory entries are found by reading the data block(s) 12 associated with a directory file for the particular directory entry that 18 By default, each directory lists its entries in an “almost-linear” 20 sense because directory entries are not split across filesystem blocks. 21 Therefore, it is more accurate to say that a directory is a series of 22 data blocks and that each block contains a linear array of directory 26 directory is of course signified by reaching the end of the file. Unused [all …]
/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/s390/cf_z14/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/s390/cf_z15/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/OK3568_Linux_fs/kernel/Documentation/filesystems/
H A D	directory-locking.rst	2 Directory Locking 6 Locking scheme used for directory operations is based on two 10 When taking the i_rwsem on multiple non-directory objects, we 16 1) read access. Locking rules: caller locks directory we are accessing. 25 4) rename() that is _not_ cross-directory. Locking rules: caller locks 28 if the target already exists, lock it. If the source is a non-directory, 37 * check that source is not a directory 43 6) cross-directory rename. The trickiest in the whole bunch. Locking 54 * If the target exists, lock it. If the source is a non-directory, 65 If no directory is its own ancestor, the scheme above is deadlock-free. [all …]
H A D	overlayfs.rst	26 non-directory objects may report an st_dev from the lower filesystem or 29 over the lifetime of a non-directory object. Many applications and 94 It would be more correct to refer to an upper and lower 'directory 96 directory trees to be in the same filesystem and there is no 113 upper and lower filesystems and refers to a non-directory in either, 117 Where both upper and lower objects are directories, a merged directory 121 "upperdir" are combined into a merged directory: 126 The "workdir" needs to be an empty directory on the same filesystem 129 Then whenever a lookup is requested in such a merged directory, the 130 lookup is performed in each actual directory and the combined result [all …]
/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/s390/cf_zec12/
H A D	extended.json	21 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 28 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 35 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 49 …"PublicDescription": "A directory write to the Level-1 Data cache where the installed cache line w… 56 …"PublicDescription": "A directory write to the Level-1 Instruction cache where the installed cache… 63 …"PublicDescription": "A directory write to the Level-1 D-Cache where the line was originally in a … 105 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/s390/cf_z196/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the returned cache … 14 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the returned cache … 42 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the returned cache … 49 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the returned cache … 56 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the returned cache … 63 …"PublicDescription": "A directory write to the Level-1 D-Cache where the line was originally in a … 70 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the returned cache … 77 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the returned cache … 91 …"PublicDescription": "A directory write to the Level-1 D-Cache where the installed cache line was … 98 …"PublicDescription": "A directory write to the Level-1 I-Cache where the installed cache line was … [all …]
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/
H A D	Working-Directory.html	17 <title>Debugging with GDB: Working Directory</title> 19 <meta name="description" content="Debugging with GDB: Working Directory"> 20 <meta name="keywords" content="Debugging with GDB: Working Directory"> 64 <a name="Working-Directory"></a> 70 <a name="Your-Program_0027s-Working-Directory"></a> 71 <h3 class="section">4.5 Your Program’s Working Directory</h3> 73 <a name="index-working-directory-_0028of-your-program_0029"></a> 75 initialized with the current working directory specified by the 76 <kbd>set cwd</kbd> command. If no directory has been specified by this 78 directory as its working directory if native debugging, or it will [all …]
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/
H A D	Working-Directory.html	17 <title>Debugging with GDB: Working Directory</title> 19 <meta name="description" content="Debugging with GDB: Working Directory"> 20 <meta name="keywords" content="Debugging with GDB: Working Directory"> 64 <a name="Working-Directory"></a> 70 <a name="Your-Program_0027s-Working-Directory"></a> 71 <h3 class="section">4.5 Your Program’s Working Directory</h3> 73 <a name="index-working-directory-_0028of-your-program_0029"></a> 75 initialized with the current working directory specified by the 76 <kbd>set cwd</kbd> command. If no directory has been specified by this 78 directory as its working directory if native debugging, or it will [all …]
/OK3568_Linux_fs/u-boot/tools/patman/
H A D	tools.py	18 """Select an output directory, ensuring it exists. 20 This either creates a temporary directory or checks that the one supplied 21 by the user is valid. For a temporary directory, it makes a note to 25 dirname: a string, name of the output directory to use to store 27 directory. 29 created temporary directory will be destroyed on exit. 32 OSError: If it cannot create the output directory. 43 raise CmdError("Cannot make output directory '%s': '%s'" % 45 tout.Debug("Using output directory '%s'" % outdir) 48 tout.Debug("Using temporary directory '%s'" % outdir) [all …]
/OK3568_Linux_fs/yocto/poky/documentation/sdk-manual/
H A D	appendix-obtain.rst	17 1. Go to the Installers Directory: Go to 63 directory:: 69 ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`" 71 ":ref:`sdk-manual/appendix-obtain:installed extensible sdk directory structure`" 87 Yocto Project :term:`Source Directory` 96 3. Initialize the Build Environment: While in the root directory of 97 the Source Directory (i.e. ``poky``), run the 106 creates the :term:`Build Directory`, 108 ``build`` in this case and is located in the Source Directory. After 109 the script runs, your current working directory is set to the [all …]
/OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/opencv-linux-armhf/include/opencv2/core/utils/
H A D	filesystem.hpp	2 // It is subject to the license terms in the LICENSE file found in the top-level directory 22 * @param path input path. Target file/directory should exist. 32 * Result entries are prefixed by base directory path. 34 * @param directory base directory 40 CV_EXPORTS void glob(const cv::String& directory, const cv::String& pattern, 47 * @param directory base directory 49 * @param[out] result globbing result with relative paths from base directory 53 CV_EXPORTS void glob_relative(const cv::String& directory, const cv::String& pattern, 66 * @brief Returns directory to store OpenCV cache files 67 * Create sub-directory in common OpenCV cache directory if it doesn't exist. [all …]
/OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/opencv-linux-aarch64/include/opencv2/core/utils/
H A D	filesystem.hpp	2 // It is subject to the license terms in the LICENSE file found in the top-level directory 22 * @param path input path. Target file/directory should exist. 32 * Result entries are prefixed by base directory path. 34 * @param directory base directory 40 CV_EXPORTS void glob(const cv::String& directory, const cv::String& pattern, 47 * @param directory base directory 49 * @param[out] result globbing result with relative paths from base directory 53 CV_EXPORTS void glob_relative(const cv::String& directory, const cv::String& pattern, 66 * @brief Returns directory to store OpenCV cache files 67 * Create sub-directory in common OpenCV cache directory if it doesn't exist. [all …]
/OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/OpenCV-android-sdk/sdk/native/jni/include/opencv2/core/utils/
H A D	filesystem.hpp	2 // It is subject to the license terms in the LICENSE file found in the top-level directory 22 * @param path input path. Target file/directory should exist. 32 * Result entries are prefixed by base directory path. 34 * @param directory base directory 40 CV_EXPORTS void glob(const cv::String& directory, const cv::String& pattern, 47 * @param directory base directory 49 * @param[out] result globbing result with relative paths from base directory 53 CV_EXPORTS void glob_relative(const cv::String& directory, const cv::String& pattern, 66 * @brief Returns directory to store OpenCV cache files 67 * Create sub-directory in common OpenCV cache directory if it doesn't exist. [all …]
/OK3568_Linux_fs/kernel/fs/isofs/
H A D	isofs.h	154 /* Every directory can have many redundant directory entries scattered 155 * throughout the directory tree. First there is the directory entry 156 * with the name of the directory stored in the parent directory. 157 * Then, there is the "." directory entry stored in the directory 158 * itself. Finally, there are possibly many ".." directory entries 164 * the many redundant entries for each directory. We normalize the 165 * block and offset by always making them point to the "." directory. 167 * Notice that we do not use the entry for the directory with the name 168 * that is located in the parent directory. Even though choosing this 169 * first directory is more natural, it is much easier to find the "." [all …]
/OK3568_Linux_fs/kernel/drivers/thunderbolt/
H A D	property.c	214 * Upon success returns the parsed directory. In case of error returns 218 * The @block is expected to be root directory. 236 * tb_property_create_dir() - Creates new property directory 237 * @uuid: UUID used to identify the particular directory 239 * Creates new, empty property directory. If @uuid is %NULL then the 240 * directory is assumed to be root directory. 286 * tb_property_free_dir() - Release memory allocated for property directory 287 * @dir: Directory to release 289 * This will release all the memory the directory occupies including all 329 /* Reserve dword padding after each directory */ in tb_property_dir_length() [all …]
/OK3568_Linux_fs/yocto/poky/bitbake/doc/bitbake-user-manual/
H A D	bitbake-user-manual-hello.rst	23 your machine, the BitBake directory appears as follows:: 44 At this point, you should have BitBake cloned to a directory that 51 directory to where your local BitBake files are and run the following 60 The recommended method to run BitBake is from a directory of your 61 choice. To be able to run BitBake from any directory, you need to add 68 Next, add the directory location 70 ``/home/scott-lenovo/bitbake/bin`` directory to the front of the 76 line while working from any directory. 117 #. Create a Project Directory: First, set up a directory for the 119 directory:: [all …]
/OK3568_Linux_fs/kernel/scripts/clang-tools/
H A D	gen_compile_commands.py	31 directory: The work directory where the objects were built. 39 directory_help = ('specify the output directory used for the kernel build ' 40 '(defaults to the working directory)') 41 parser.add_argument('-d', '--directory', type=str, default='.', 59 'If nothing is specified, the current directory is searched') 65 os.path.abspath(args.directory), 68 args.paths if len(args.paths) > 0 else [args.directory]) 71 def cmdfiles_in_dir(directory): argument 72 """Generate the iterator of .cmd files found under the directory. 74 Walk under the given directory, and yield every .cmd file found. [all …]
/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/s390/cf_z10/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the returned cache … 14 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the installed cache… 21 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the installed cache… 28 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the installtion cac… 35 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the installed cache… 42 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the installed cache… 49 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the installed cache… 56 …"PublicDescription": "A directory write to the Level-1 I-Cache where the installed cache line was … 63 …"PublicDescription": "A directory write to the Level-1 D-Cache where the line was originally in a …
/OK3568_Linux_fs/external/chromium/licenses/
H A D	README	20 When you unpack the newlib-2.0.0.tar.gz file, you'll find a directory 74 `newlib-VERSION-NUMBER/texinfo' directory. 81 To compile NEWLIB, you must build it in a directory separate from 82 the source directory. If you want to run NEWLIB versions for several host 90 To build `newlib' in a specific directory, run `configure' with the 93 directory. If the path to `configure' would be the same as the 98 directory for a Sun 4 cross m68k-aout environment like this: 107 directory, it creates a tree for the binaries with the same structure 108 (and using the same names) as the tree under the source directory. In 110 directory `newlib-m68k-aout/libiberty', and NEWLIB itself in [all …]
/OK3568_Linux_fs/u-boot/include/
H A D	fs.h	51 * in directory "dirname". 102 * Directory entry types, matches the subset of DT_x in posix readdir() 105 #define FS_DT_DIR 4 /* directory / 110 A directory entry, returned by fs_readdir(). Returns information 111 * about the file/directory at the current directory entry position. 127 * fs_opendir - Open a directory 129 * @filename: the path to directory to open 130 * @return a pointer to the directory stream or NULL on error and errno 136 * fs_readdir - Read the next directory entry in the directory stream. 139 * directory entry is no longer valid after calling fs_readdir() again. [all …]
/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/dpkg/dpkg/
H A D	0001-Dpkg-Source-Archive-Prevent-directory-traversal-for-.patch	4 Subject: [PATCH] Dpkg::Source::Archive: Prevent directory traversal for 9 which can lead to directory traversal situations on specially crafted 14 itself is not present as an actual directory on the tarball. 17 out of the source tree root directory, and then a debian.tar that 18 contains an entry within that symlink as if it was a directory, without 19 a directory entry for the symlink pathname itself, which will be 29 instead still use a temporary directory, then walk that directory and 30 remove any matching entry in the destination directory, replicating what 31 GNU tar would do, but in addition avoiding the directory traversal issue 76 - mkdir($dest) or syserr(g_('cannot create directory %s'), $dest); [all …]

12 3 4 5 6 7 8 9 10 >>...221