Searched refs:stored (Results 1 – 25 of 402) sorted by relevance
12345678910>>...17
| /Linux-v5.4/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)
|
| D | sysfs-class-rc-nuvoton | 6 Reading this file returns the stored CIR wakeup sequence.
12 Note: Some systems reset the stored wakeup sequence to a
|
| D | sysfs-class-backlight-driver-adp8870 | 13 will also show the brightness level stored for this
28 This file will also show the dim brightness level stored for
54 It can be enabled by writing the value stored in
|
| D | sysfs-bus-iio-isl29501 | 37 stored in in_proximity0_calib_phase_temp_a and
47 The value stored in sensor is displayed when read from.
|
| /Linux-v5.4/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 | 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
|
| 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.
|
| /Linux-v5.4/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.4/Documentation/filesystems/ |
| D | squashfs.txt | 104 these are stored here.
127 information has to be stored.
132 Like inodes, directories are packed into compressed metadata blocks, stored
164 of each datablock is stored in a block list contained within the
183 fragment lookup table is itself stored compressed into metadata blocks.
193 stored compressed into metadata blocks. A second index table is used to
207 This table is stored compressed into metadata blocks. A second index table is
215 for each inode are stored in a list, each list entry containing a type,
219 is stored inline (in which case the value field contains the xattr value),
220 or if it is stored out of line (in which case the value field stores a
[all …]
|
| D | qnx6.txt | 49 Each of these root nodes holds information like total size of the stored
60 Data leaves are always on the lowest level. So no data is stored on upper
90 The filesize is stored 64bit. Inode counting starts with 1. (while long
105 record plus the longfile inode number also stored in that record.
127 Long filenames are stored in a separate addressing tree. The staring point
133 is a limit of 510 bytes for the actual filename stored.
138 The qnx6fs filesystem allocation bitmap is stored in a tree under bitmap
|
| D | ubifs-authentication.rst | 13 is a lost smartphone where the attacker is unable to read personal data stored
21 most of the filesystem metadata of UBIFS is stored in plain, this makes it
106 the index is not stored in a single place on the flash, but *wanders* around
137 ``mkfs.ubifs``) and stored in the superblock node. The log area contains only
206 the authenticity and integrity of metadata and file contents stored on flash.
241 stored on flash are authenticated. That is:
360 The location of the log area is stored in the master node. Since the master
363 the filesystem is created using `mkfs.ubifs` and stored in the superblock node.
364 To avoid tampering with this and other values stored there, a HMAC is added to
365 the superblock struct. The superblock node is stored in LEB 0 and is only
[all …]
|
| /Linux-v5.4/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.4/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.4/Documentation/media/uapi/v4l/ |
| D | pixfmt-inzi.rst | 29 The first plane - Infrared data - is stored according to
31 Each pixel is 16-bit cell, with actual data stored in the 10 LSBs
41 Each cell is a 16-bit word with more significant data stored at higher
|
| D | pixfmt-y10.rst | 24 stored in 16-bit words with unused high bits padded with 0. The least
25 significant byte is stored at lower memory addresses (little-endian).
|
| D | pixfmt-y12.rst | 24 stored in 16-bit words with unused high bits padded with 0. The least
25 significant byte is stored at lower memory addresses (little-endian).
|
| D | pixfmt-srggb16.rst | 28 sample. Each sample is stored in a 16-bit word. Each n-pixel row contains
30 rows. Bytes are stored in memory in little endian order. They are
|
| D | pixfmt-intro.rst | 23 data can still be stored and retrieved in the proprietary format. For
51 For some formats, data is stored in separate, discontiguous memory
54 :ref:`YUV422 <V4L2-PIX-FMT-YUV422M>` frame is normally stored in one
|
| D | pixfmt-srggb10.rst | 30 sample. Each sample is stored in a 16-bit word, with 6 unused
33 stored in memory in little endian order. They are conventionally described
|
| /Linux-v5.4/arch/arm/nwfpe/ |
| D | softfloat-macros | 39 The result is stored in the location pointed to by `zPtr'.
64 The result is stored in the location pointed to by `zPtr'.
89 64 nonzero bits; this is stored at the location pointed to by `z0Ptr'. The
93 bits shifted off were all zero. This extra result is stored in the location
138 which are stored at the locations pointed to by `z0Ptr' and `z1Ptr'.
173 nonzero. The result is broken into two 64-bit pieces which are stored at
214 stored at the locations pointed to by `z0Ptr' and `z1Ptr'. The bits shifted
218 were all zero. This extra result is stored in the location pointed to by
285 pieces which are stored at the locations pointed to by `z0Ptr' and `z1Ptr'.
304 64-bit pieces which are stored at the locations pointed to by `z0Ptr',
[all …]
|
| /Linux-v5.4/Documentation/networking/ |
| D | devlink-health.txt | 29 there is no other dump which is already stored)
52 Retrieves the last stored dump. Devlink health
53 saves a single dump. If an dump is not already stored by the devlink
|
| /Linux-v5.4/Documentation/vm/ |
| D | zswap.rst | 48 back into memory all of the pages stored in the compressed pool. The
49 pages stored in zswap will remain in the compressed pool until they are
90 Once there are no PTEs referencing a swap page stored in zswap (i.e. the count
118 value is stored.
130 existing pages which are marked as same-value filled pages remain stored
134 of pages stored, same-value filled pages and various counters for the reasons
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| D | x_ovfl.S | 14 | If the instruction is move_out, then garbage is stored in the
17 | following values should be stored at the destination, based
|
| /Linux-v5.4/arch/x86/crypto/ |
| D | crc32c-pcl-intel-asm_64.S | 287 less_than_8: # Length should be stored in
295 less_than_4: # Length should be stored in
302 less_than_2: # Length should be stored in the MSB
|
| /Linux-v5.4/Documentation/arm/nwfpe/ |
| D | notes.rst | 14 I was looking at some code, that calculated a double result, stored it in f4
19 converted to extended, then stored. If an lfm/sfm combination had been used,
|
12345678910>>...17
