Searched +full:block +full:- +full:offset (Results 1 – 25 of 269) sorted by relevance
1234567891011
| /Documentation/admin-guide/device-mapper/ |
| D | dm-ebs.rst | 2 dm-ebs
7 a smaller logical block size on a device with a larger logical block
11 Supported emulated logical block sizes 512, 1024, 2048 and 4096.
13 Underlying block size can be set to > 4K to test buffering larger units.
17 ----------------
18 <dev path> <offset> <emulated sectors> [<underlying sectors>]
23 Full pathname to the underlying block-device,
24 or a "major:minor" device-number.
25 <offset>:
29 Number of sectors defining the logical block size to be emulated;
[all …]
|
| D | linear.rst | 2 dm-linear
5 Device-Mapper's "linear" target maps a linear range of the Device-Mapper
7 block of logical volume managers.
9 Parameters: <dev path> <offset>
11 Full pathname to the underlying block-device, or a
12 "major:minor" device-number.
13 <offset>:
24 echo "0 `blockdev --getsz $1` linear $1 0" | dmsetup create identity
30 size1=`blockdev --getsz $1`
31 size2=`blockdev --getsz $2`
[all …]
|
| D | dm-dust.rst | 1 dm-dust
15 in the "bad block list" will fail with EIO ("Input/output error").
17 Writes of blocks in the "bad block list will result in the following:
19 1. Remove the block from the "bad block list".
27 With dm-dust, the user can use the "addbadblock" and "removebadblock"
31 This allows the pre-writing of test data and metadata prior to
35 ----------------
36 <device_path> <offset> <blksz>
40 Path to the block device.
42 <offset>:
[all …]
|
| D | verity.rst | 2 dm-verity
5 Device-Mapper's "verity" target provides transparent integrity checking of
6 block devices using a cryptographic digest provided by the kernel crypto API.
7 This target is read-only.
21 This is the type of the on-disk hash format.
25 the rest of the block is padded with zeroes.
40 dm-verity device.
43 The block size on a data device in bytes.
44 Each block corresponds to one digest on the hash device.
47 The size of a hash block in bytes.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-block-loop | 1 What: /sys/block/loopX/loop/autoclear
4 Contact: linux-block@vger.kernel.org
8 self-distruct after last close.
10 What: /sys/block/loopX/loop/backing_file
13 Contact: linux-block@vger.kernel.org
18 What: /sys/block/loopX/loop/offset
21 Contact: linux-block@vger.kernel.org
23 (RO) Start offset (in bytes).
25 What: /sys/block/loopX/loop/sizelimit
28 Contact: linux-block@vger.kernel.org
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | fsl-qdma.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/fsl-qdma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Li <Frank.Li@nxp.com>
15 - const: fsl,ls1021a-qdma
16 - items:
17 - enum:
18 - fsl,ls1028a-qdma
19 - fsl,ls1043a-qdma
[all …]
|
| /Documentation/block/ |
| D | cmdline-partition.rst | 6 block device partition table from the kernel command line.
8 It is typically used for fixed block (eMMC) embedded devices.
10 by absolute address of data on the block device.
15 blkdevparts=<blkdev-def>[;<blkdev-def>]
16 <blkdev-def> := <blkdev-id>:<partdef>[,<partdef>]
17 <partdef> := <size>[@<offset>](part-name)
19 <blkdev-id>
20 block device disk name. Embedded device uses fixed block device.
29 "-" is used to denote all remaining space.
31 <offset>
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | directory.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -----------------
9 that reference the same inode number--these are known as hard links, and
11 such, directory entries are found by reading the data block(s)
18 By default, each directory lists its entries in an “almost-linear”
22 data blocks and that each block contains a linear array of directory
23 entries. The end of each per-block array is signified by reaching the
24 end of the block; the last entry in the block has a record length that
25 takes it all the way to the end of the block. The end of the entire
36 .. list-table::
[all …]
|
| D | ifork.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------------------
8 regular files and directories will use it for file block indexing
15 string is less than 60 bytes long. Otherwise, either extents or block
18 Direct/Indirect Block Addressing
21 In ext2/3, file block numbers were mapped to logical block numbers by
22 means of an (up to) three level 1-1 block map. To find the logical block
23 that stores a particular file block, the code would navigate through
26 block isn't full of garbage.
36 Note that with this block mapping scheme, it is necessary to fill out a
[all …]
|
| D | journal.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 --------------
10 “important” data writes on-disk as quickly as possible. Once the important
15 read-write-erases) before erasing the commit record. Should the system
45 consumes an entire block group, though mke2fs tries to put it in the
48 All fields in jbd2 are written to disk in big-endian order. This is the
61 .. list-table::
63 :header-rows: 1
65 * - Superblock
66 - descriptor_block (data_blocks or revocation_block) [more data or
[all …]
|
| D | attributes.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -------------------
7 block on the disk and referenced from inodes via ``inode.i_file_acl*``.
17 sb.inode_size = 256, then there are 256 - (128 + 28) = 100 bytes
18 available for in-inode extended attribute storage. The second place
19 where extended attributes can be found is in the block pointed to by
21 block to contain a pointer to a second extended attribute block (or even
23 attribute's value to be stored in a separate data block, though as of
32 .. list-table::
34 :header-rows: 1
[all …]
|
| D | inodes.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -----------
7 pertaining to the file (time stamps, block maps, extended attributes,
15 links and is in general more seek-happy than ext4 due to its simpler
16 block allocator and extensive use of linked lists.)
21 block group containing an inode can be calculated as
22 ``(inode_number - 1) / sb.s_inodes_per_group``, and the offset into the
23 group's table is ``(inode_number - 1) % sb.s_inodes_per_group``. There
31 .. list-table::
33 :header-rows: 1
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | keystone-reset.txt | 8 block. The Reset Mux block can be configured to cause reset or not.
14 - compatible: ti,keystone-reset
16 - ti,syscon-pll: phandle/offset pair. The phandle to syscon used to
17 access pll controller registers and the offset to use
20 - ti,syscon-dev: phandle/offset pair. The phandle to syscon used to
21 access device state control registers and the offset
22 in order to use mux block registers for all watchdogs.
26 - ti,soft-reset: Boolean option indicating soft reset.
29 - ti,wdt-list: WDT list that can cause SoC reset. It's not related
40 pllctrl: pll-controller@2310000 {
[all …]
|
| /Documentation/iio/ |
| D | ad4695.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
26 ----------------
30 4-wire mode
35 .. code-block::
37 +-------------+ +-------------+
38 | CS |<-+------| CS |
39 | CNV |<-+ | |
42 | SDI |<--------| SDO |
43 | SDO |-------->| SDI |
44 | SCLK |<--------| SCLK |
[all …]
|
| /Documentation/bpf/ |
| D | llvm_reloc.rst | 1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
12 LLVM BPF backend records each relocation with the following 16-byte
17 Elf64_Addr r_offset; // Offset from the beginning of section.
31 Compiled with ``clang --target=bpf -O2 -c test.c``, the following is
32 the code with ``llvm-objdump -dr test.o``::
52 The following ``llvm-readelf -r test.o`` shows the binary values of the four
55 Relocation section '.rel.text' at offset 0x190 contains 4 entries:
56 Offset Info Type Symbol's Value Symbol's Name
62 Each relocation is represented by ``Offset`` (8 bytes) and ``Info`` (8 bytes).
64 (Offset 0x0) and the corresponding ``Info`` indicates the relocation type
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | chromeos-acpi-device.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 .. flat-table:: Supported ACPI Objects
13 :header-rows: 1
15 * - Object
16 - Description
18 * - CHSW
19 - Chrome OS switch positions
21 * - HWID
22 - Chrome OS hardware ID
24 * - FWID
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | atmel-nand.txt | 4 Documentation/devicetree/bindings/memory-controllers/atmel,ebi.txt).
11 - compatible: should be one of the following
12 "atmel,at91rm9200-nand-controller"
13 "atmel,at91sam9260-nand-controller"
14 "atmel,at91sam9261-nand-controller"
15 "atmel,at91sam9g45-nand-controller"
16 "atmel,sama5d3-nand-controller"
17 "microchip,sam9x60-nand-controller"
18 - ranges: empty ranges property to forward EBI ranges definitions.
19 - #address-cells: should be set to 2.
[all …]
|
| D | davinci-nand.txt | 7 Davinci DM646x - https://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
8 Kestone - https://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
12 - compatible: "ti,davinci-nand"
13 "ti,keystone-nand"
15 - reg: Contains 2 offset/length values:
16 - offset and length for the access window.
17 - offset and length for accessing the AEMIF
20 - ti,davinci-chipselect: number of chipselect. Indicates on the
23 Can be in the range [0-3].
27 - ti,davinci-mask-ale: mask for ALE. Needed for executing address
[all …]
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | st,stm32-rproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/st,stm32-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 - Fabien Dessenne <fabien.dessenne@foss.st.com>
15 - Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
19 const: st,stm32mp1-m4
31 reset-names:
33 - const: mcu_rst
34 - const: hold_boot
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | dcsr.txt | 8 the integration of the block with the rest of the chip.
21 - compatible
24 Definition: Must include "fsl,dcsr" and "simple-bus".
25 The DCSR space exists in the memory-mapped bus.
27 - #address-cells
33 - #size-cells
40 - ranges
42 Value type: <prop-encoded-array>
48 #address-cells = <1>;
49 #size-cells = <1>;
[all …]
|
| /Documentation/filesystems/ |
| D | fiemap.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 extent mappings. Instead of block-by-block mapping (such as bmap), fiemap
13 --------------
18 __u64 fm_start; /* logical offset (inclusive) at
33 those on disk - that is, the logical offset of the 1st returned extent
65 --------------
83 __u64 fe_logical; /* logical offset in bytes for the start of
85 __u64 fe_physical; /* physical offset in bytes for the start
94 for an extents logical offset to start before the request or its logical
97 block size of the file system. With the exception of extents flagged as
[all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | atmel,at91sam9260-rtt.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/rtc/atmel,at91sam9260-rtt.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - $ref: rtc.yaml#
14 - Alexandre Belloni <alexandre.belloni@bootlin.com>
19 - items:
20 - const: atmel,at91sam9260-rtt
21 - items:
22 - enum:
[all …]
|
| /Documentation/devicetree/bindings/soc/fsl/ |
| D | guts.txt | 1 * Global Utilities Block
3 The global utilities block controls power management, I/O device
4 enabling, power-on-reset configuration monitoring, general-purpose
10 - compatible : Should define the compatible device type for
11 global-utilities.
13 "fsl,qoriq-device-config-1.0"
14 "fsl,qoriq-device-config-2.0"
15 "fsl,<chip>-device-config"
16 "fsl,<chip>-guts"
17 - reg : Offset and length of the register set for the device.
[all …]
|
| /Documentation/driver-api/ |
| D | mtdnand.rst | 10 The generic NAND driver supports almost all NAND and AG-AND based chips
31 --------------------------
37 - [MTD Interface]
43 - [NAND Interface]
48 - [GENERIC]
53 - [DEFAULT]
65 -------------------------------
71 - [INTERN]
77 - [REPLACEABLE]
86 - [BOARDSPECIFIC]
[all …]
|
| /Documentation/devicetree/bindings/reset/ |
| D | hisilicon,hi3660-reset.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reset/hisilicon,hi3660-reset.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Wei Xu <xuwei5@hisilicon.com>
15 The reset controller registers are part of the system-ctl block on
21 - items:
22 - const: hisilicon,hi3660-reset
23 - items:
24 - const: hisilicon,hi3670-reset
[all …]
|
1234567891011