| /Linux-v5.10/Documentation/networking/devlink/ |
| D | nfp.rst | 46 - stored, running
49 - stored, running
52 - stored, running
55 - stored, running
58 - stored, running
61 - stored, running
64 - stored, running
|
| D | bnxt.rst | 64 - stored, running
67 - stored, running
70 - stored, running
76 - stored, running
79 - stored, running
|
| D | devlink-info.rst | 73 * - ``stored``
76 Stored values must update to reflect changes in the flash even
78 ``stored`` versions when new software is flashed, it must not report
82 components stored on the flash should feature in both the ``running`` and
83 ``stored`` sections, if device is capable of reporting ``stored`` versions
119 ``bundle_id`` can appear in both ``running`` and ``stored`` versions,
|
| D | devlink-flash.rst | 61 On-disk firmware files are usually stored in ``/lib/firmware/``.
71 (``fixed``, ``running``, ``stored``).
79 ``running`` and ``stored`` firmware versions identify the firmware running
95 if $want_flash_vers != devlink-dev-info['stored']:
|
| /Linux-v5.10/Documentation/filesystems/ext4/ |
| D | attributes.rst | 6 Extended attributes (xattrs) are typically stored in a separate data
23 attribute's value to be stored in a separate data block, though as of
29 Extended attributes, when stored after the inode, have a header
89 long. When stored in an external block, the ``struct ext4_xattr_entry``
90 entries must be stored in sorted order. The sort order is
92 Attributes stored inside an inode do not need be stored in sorted order.
113 - Location of this attribute's value on the disk block where it is stored.
120 - The inode where the value is stored. Zero indicates the value is in the
141 are stored starting at the end of the block and grow towards the
188 POSIX ACLs are stored in a reduced version of the Linux kernel (and
[all …]
|
| D | checksums.rst | 11 lower 16 bits are stored. Enabling the 64bit feature increases the data
12 structure size so that full 32-bit checksums can be stored for many data
62 - UUID + the entire bitmap. Checksums are stored in the group descriptor,
72 descriptor). In all cases, only the lower 16 bits are stored.
|
| D | verity.rst | 12 stored after the end of the file data itself, in the following format:
19 <fsverity_merkle_tree>`, with the tree levels stored in order from
20 root to leaf, and the tree blocks within each level stored in their
|
| /Linux-v5.10/fs/nls/ |
| D | Kconfig | 44 native language character sets. These character sets are stored
56 native language character sets. These character sets are stored
68 native language character sets. These character sets are stored
81 native language character sets. These character sets are stored in
97 native language character sets. These character sets are stored in
112 native language character sets. These character sets are stored in
123 native language character sets. These character sets are stored in
134 native language character sets. These character sets are stored in
145 native language character sets. These character sets are stored in
156 native language character sets. These character sets are stored in
[all …]
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-class-switchtec | 18 Description: Component identifier as stored in the hardware (eg. PM8543)
27 Description: Component revision stored in the hardware (read only)
35 Description: Component vendor as stored in the hardware (eg. MICROSEM)
44 Description: Device version as stored in the hardware (read only)
76 Description: Product identifier as stored in the hardware (eg. PSX 48XG3)
85 Description: Product revision stored in the hardware (eg. RevB)
94 Description: Product vendor as stored in the hardware (eg. MICROSEM)
|
| /Linux-v5.10/Documentation/fb/ |
| D | api.rst | 46 Pixels are stored in memory in hardware-dependent formats. Applications need
51 additional information, which are stored in the variable screen information
55 macropixels. Types describe how macropixels are stored in memory. The following
60 Macropixels are stored contiguously in a single plane. If the number of bits
83 belonging to different planes, is stored in the fixed screen information
88 Macropixels are stored in memory as described by the format FOURCC identifier
89 stored in the variable screen information grayscale field.
93 Pixels are black or white and stored on a number of bits (typically one)
104 Pixels are black or white and stored on a number of bits (typically one)
119 Each component is stored in a macropixel according to the variable screen
[all …]
|
| /Linux-v5.10/arch/nios2/include/asm/ |
| D | asm-macros.h | 92 * bit is zero. The result of the bit test is stored in reg1.
104 * bit is non-zero. The result of the bit test is stored in reg1.
116 * The result of the bit test is stored in reg1.
137 * The result of the bit test is stored in reg1.
158 * The result of the bit test is stored in reg1.
179 * The result of the bit test is stored in reg1. If the
192 * The result of the bit test is stored in reg1. If the
205 * The result of the bit test is stored in reg1. If the
218 * The result of the bit test is stored in reg1. If the
231 * The result of the bit test is stored in reg1. If the
[all …]
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | squashfs.rst | 110 these are stored here.
133 information has to be stored.
138 Like inodes, directories are packed into compressed metadata blocks, stored
170 of each datablock is stored in a block list contained within the
189 fragment lookup table is itself stored compressed into metadata blocks.
199 stored compressed into metadata blocks. A second index table is used to
213 This table is stored compressed into metadata blocks. A second index table is
221 for each inode are stored in a list, each list entry containing a type,
225 is stored inline (in which case the value field contains the xattr value),
226 or if it is stored out of line (in which case the value field stores a
[all …]
|
| D | qnx6.rst | 55 Each of these root nodes holds information like total size of the stored
68 Data leaves are always on the lowest level. So no data is stored on upper
100 The filesize is stored 64bit. Inode counting starts with 1. (while long
119 record plus the longfile inode number also stored in that record.
143 Long filenames are stored in a separate addressing tree. The staring point
151 is a limit of 510 bytes for the actual filename stored.
156 The qnx6fs filesystem allocation bitmap is stored in a tree under bitmap
|
| D | ubifs-authentication.rst | 17 is a lost smartphone where the attacker is unable to read personal data stored
25 most of the filesystem metadata of UBIFS is stored in plain, this makes it
110 the index is not stored in a single place on the flash, but *wanders* around
141 ``mkfs.ubifs``) and stored in the superblock node. The log area contains only
210 the authenticity and integrity of metadata and file contents stored on flash.
245 stored on flash are authenticated. That is:
364 The location of the log area is stored in the master node. Since the master
367 the filesystem is created using `mkfs.ubifs` and stored in the superblock node.
368 To avoid tampering with this and other values stored there, a HMAC is added to
369 the superblock struct. The superblock node is stored in LEB 0 and is only
[all …]
|
| /Linux-v5.10/kernel/ |
| D | stacktrace.c | 109 * Return: Number of trace entries stored.
133 * Return: Number of trace entries stored.
161 * Return: Number of trace entries stored.
186 * reliable and returns the number of entries stored.
219 * Return: Number of trace entries stored.
267 * Return: Number of trace entries stored
290 * Return: Number of trace entries stored
314 * Return: Number of trace entries stored
338 * reliable and returns the number of entries stored.
361 * Return: Number of trace entries stored
|
| /Linux-v5.10/drivers/char/mwave/ |
| D | README | 18 If the dsp irq has not been setup and stored in bios by the
23 If the dsp io range has not been setup and stored in bios by the
28 If the mwave's uart irq has not been setup and stored in bios by the
33 If the uart io range has not been setup and stored in bios by the
|
| /Linux-v5.10/lib/zlib_inflate/ |
| D | inflate.h | 31 STORED, /* i: waiting for stored size (length and complement) */ enumerator
32 COPY, /* i/o: waiting for input or output to copy stored block */
62 TYPE -> STORED or TABLE or LEN or CHECK
63 STORED -> COPY -> TYPE
93 /* for string and stored block copying */
|
| /Linux-v5.10/arch/x86/math-emu/ |
| D | load_store.c | 167 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
177 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
187 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
213 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
220 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
227 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
234 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
289 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
303 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
317 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
|
| /Linux-v5.10/Documentation/vm/ |
| D | zswap.rst | 50 back into memory all of the pages stored in the compressed pool. The
51 pages stored in zswap will remain in the compressed pool until they are
93 Once there are no PTEs referencing a swap page stored in zswap (i.e. the count
122 value is stored.
134 existing pages which are marked as same-value filled pages remain stored
151 of pages stored, same-value filled pages and various counters for the reasons
|
| /Linux-v5.10/drivers/block/zram/ |
| D | zram_drv.h | 49 ZRAM_WB, /* page is stored on backing_device */
72 atomic64_t compr_data_size; /* compressed size of pages stored */
81 atomic64_t pages_stored; /* no. of pages currently stored */
82 atomic_long_t max_used_pages; /* no. of maximum pages stored */
|
| /Linux-v5.10/include/linux/netfilter_ipv6/ |
| D | ip6_tables.h | 11 * src, dst, src_mask, dst_mask are always stored in network byte order.
12 * flags are stored in host byte order (of course).
13 * Port numbers are stored in HOST byte order.
|
| /Linux-v5.10/Documentation/dev-tools/ |
| D | kmemleak.rst | 70 these actions are stored in an early log buffer. The size of this buffer
86 information like size and stack trace, are stored in a rbtree.
102 the values against the addresses stored in the rbtree. If
111 Some allocated memory blocks have pointers stored in the kernel's
197 systems, because of pointers temporarily stored in CPU registers or
215 Another source of false negatives is the data stored in non-pointer
223 macro or the pointer is stored in a location not scanned by kmemleak.
|
| /Linux-v5.10/arch/arm/lib/ |
| D | backtrace-clang.S | 73 * The stored locals for dump_stack are in dump_stack's frame. This means that
78 * function prologue opcodes we can determine which variables are stored in the
81 * To find the function start of dump_stack we can look at the stored LR of
177 * registers were stored in the function prologue.
181 * continue as if there had been no registers stored in this frame.
186 ldr r0, [frame] @ locals are stored in
|
| /Linux-v5.10/include/linux/netfilter_ipv4/ |
| D | ip_tables.h | 11 * src, dst, src_mask, dst_mask are always stored in network byte order.
12 * flags are stored in host byte order (of course).
13 * Port numbers are stored in HOST byte order.
|
| /Linux-v5.10/tools/testing/selftests/livepatch/ |
| D | test-state.sh | 39 $MOD_LIVEPATCH: free_loglevel_state: freeing space for the stored console_loglevel
82 $MOD_LIVEPATCH2: free_loglevel_state: freeing space for the stored console_loglevel
137 $MOD_LIVEPATCH2: free_loglevel_state: freeing space for the stored console_loglevel
172 $MOD_LIVEPATCH2: free_loglevel_state: freeing space for the stored console_loglevel
|
