Searched full:partition (Results 1 – 25 of 167) sorted by relevance
1234567
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | fixed-partitions.yaml | 12 on-flash partition table such as RedBoot.
14 The partition table should be a node named "partitions". Partitions are then
35 Compression algorithm used to store the data in this partition, chosen
52 $ref: partition.yaml#
56 description: Partition id in Sercomm partition map. Mtd parser
57 uses this id to find a record in the partition map containing
58 offset and size of the current partition. The values from
59 partition map overrides partition offset and size defined in
77 partition@0 {
95 /* a 4 GiB partition */
[all …]
|
| D | partition.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/partition.yaml#
7 title: Partition
10 This binding describes a single flash partition. Each partition must have its
11 relative offset and size specified. Depending on partition function extra
14 A partition may be dynamically allocated by a specific parser at runtime.
16 Everything after 'partition-' will be used as the partition name to compare
18 If the partition contains invalid char a label can be provided that will
20 This is used to assign an OF node to the dynamiccally allocated partition
22 The OF node will be assigned only if the partition label declared match the
30 description: partition's offset and size within the flash
[all …]
|
| D | u-boot.yaml | 7 title: U-Boot bootloader partition
20 - $ref: partition.yaml#
27 Broadcom stores environment variables inside a U-Boot partition. They
31 "^partition-.*$":
32 $ref: partition.yaml#
43 partition@0 {
48 partition-u-boot-env {
52 partition@100000 {
|
| D | qcom,smem-part.yaml | 7 title: Qualcomm SMEM NAND flash partition parser
14 Memory (SMEM) based partition table scheme. The maximum partitions supported
15 varies between partition table revisions. V3 supports maximum 16 partitions
25 "^partition-[0-9a-z]+$":
42 /* Example declaring dynamic partition */
47 partition-art {
|
| D | brcm,bcm4908-partitions.yaml | 33 "^partition@[0-9a-f]+$":
34 $ref: partition.yaml#
53 partition@0 {
58 partition@100000 {
63 partition@1000000 {
68 partition@1f00000 {
|
| D | linksys,ns-partitions.yaml | 34 "^partition@[0-9a-f]+$":
35 $ref: partition.yaml#
56 partition@0 {
62 partition@100000 {
67 partition@200000 {
72 partition@1100000 {
|
| D | seama.yaml | 9 description: The SEAttle iMAge (SEAMA) partition is a type of partition
13 (MIPS), Broadcom BCM53xx, and RAMIPS platforms. This partition type
18 - $ref: partition.yaml#
39 partition@0 {
|
| D | binman.yaml | 10 This corresponds to a binman 'entry'. It is a single partition which holds
14 partition. There are quite a number of binman-specific entry types, such as
21 - $ref: /schemas/mtd/partitions/partition.yaml#
41 partition@100000 {
48 partition@200000 {
|
| D | brcm,bcm963xx-cfe-nor-partitions.txt | 6 NVRAM partition, and the remainder in-between for one to two firmware partitions
7 at fixed offsets. A valid firmware partition is identified by the ImageTag
9 kernel offsets and sizes within the firmware partition.
|
| D | brcm,bcm963xx-imagetag.txt | 1 Broadcom BCM963XX ImageTag Partition Container
5 partitions or non standard bootloader partition sizes. For these a mixed layout
6 needs to be used with an explicit firmware partition.
|
| D | partitions.yaml | 11 node. All partition parsers must be referenced here.
36 "^partition(-.+|@[0-9a-f]+)$":
37 $ref: partition.yaml
|
| D | brcm,trx.txt | 1 Broadcom TRX Container Partition
13 Container can hold up to 4 partitions. The first partition has to contain a
18 TRX doesn't enforce any strict partition boundaries or size limits. All
|
| /Documentation/block/ |
| D | cmdline-partition.rst | 2 Embedded device command line partition parsing
6 block device partition table from the kernel command line.
11 Users can easily change the partition.
24 partition size, in bytes, such as: 512, 1m, 1G.
32 partition start address, in bytes.
38 partition name. Kernel sends uevent with "PARTNAME". Application can
39 create a link to block device partition with the name "PARTNAME".
40 User space application can access partition by partition name.
|
| /Documentation/misc-devices/ |
| D | ibmvmc.rst | 24 interface between the hypervisor and a management partition. This interface
25 is like a message passing interface. This management partition is intended
38 In the management partition, a management application exists which enables
43 The management application runs on a Linux logical partition on a
49 functions implemented by the HMC and enables basic partition configuration.
54 The VMC enables the management partition to provide basic partitioning
59 - Display of partition status
70 software. This device is presented to a designated management partition as
76 management partition sides of the channel are running prior to
83 Administrative messages are used for each partition using the VMC to
[all …]
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | u-boot,env.yaml | 18 1. Raw flash partition
42 description: Partition offset and size for env on top of MTD
65 pattern: "^partition@[0-9a-f]+$"
79 partition@0 {
85 env: partition@40000 {
100 partition@0 {
105 partition-u-boot-env {
114 partition@0 {
|
| /Documentation/power/ |
| D | swsusp-and-swap-files.rst | 11 (2) the header of a swap file is not in the first block of the partition that
20 identify a swap file swsusp uses the name of the partition that holds the file
21 and the offset from the beginning of the partition at which the swap file's
35 offset, in <PAGE_SIZE> units, from the beginning of the partition which
42 where <swap_file_partition> is the partition on which the swap file is located
50 Use a userland suspend application that will set the partition and offset
57 partition. In particular, the swap file has to be active (ie. be present in
|
| D | userland-swsusp.rst | 81 allocate a swap page from the resume partition
90 set the resume partition and the offset (in <PAGE_SIZE>
91 units) from the beginning of the partition at which the swap header is
137 snapshot image from/to the kernel will use a swap partition, called the resume
138 partition, or a swap file as storage space (if a swap file is used, the resume
139 partition is the partition that holds this file). However, this is not really
140 required, as they can use, for example, a special (blank) suspend partition or
141 a file on a partition that is unmounted before SNAPSHOT_CREATE_IMAGE and
|
| /Documentation/devicetree/bindings/mtd/ |
| D | orion-nand.txt | 30 partition@0 {
36 partition@100000 {
41 partition@300000 {
46 partition@400000 {
|
| D | ibm,ndfc.txt | 12 - partition(s) - follows the OF MTD standard for partitions
28 partition@0 {
32 partition@200000 {
|
| D | samsung-s3c2410.txt | 21 which further contains sub-nodes describing the flash partition mapping.
45 partition@0 {
50 partition@40000 {
|
| D | ingenic,nand.yaml | 112 partition@0 {
117 partition@800000 {
122 partition@a00000 {
127 partition@c00000 {
132 partition@4c00000 {
|
| D | hisi504-nand.txt | 12 - #address-cells: Partition address, should be set 1.
13 - #size-cells: Partition size, should be set 1.
40 partition@0 {
|
| /Documentation/admin-guide/ |
| D | iostats.rst | 137 read I/Os issued per partition should equal those made to the disks ...
154 a disk address relative to a partition to the disk address relative to
156 at the disk level rather than at both the disk and partition level as
162 This is the total number of reads issued to this partition.
166 partition.
169 This is the total number of writes issued to this partition.
173 this partition.
176 record of the partition-relative address is kept, the subsequent success
177 or failure of the read cannot be attributed to the partition. In other
189 disk and partition statistics are consistent again. Since we still don't
[all …]
|
| /Documentation/driver-api/mmc/ |
| D | mmc-tools.rst | 19 - Create general purpose partition.
21 - Enable write reliability per partition.
23 - Enable the boot partition.
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-sgi_uv | 29 The partition_id entry contains the partition id.
31 machines, which each partition running a unique copy
32 of the operating system. Each partition will have a unique
33 partition id.
38 this partition is in.
92 the corresponding hub is local to the current partition.
|
1234567