Searched full:partitions (Results 1 – 25 of 109) sorted by relevance
12345
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | tplink,safeloader-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/tplink,safeloader-partitions.yaml#
7 title: TP-Link SafeLoader partitions
19 Partitions specified in partitions table cover whole flash space. Some
22 partitions contain fully changeable content (like rootfs).
25 based partitions table. That offset is picked at manufacturing process
33 const: tplink,safeloader-partitions
35 partitions-table-offset:
36 description: Flash offset of partitions table
44 - partitions-table-offset
50 partitions {
[all …]
|
| D | brcm,bcm947xx-cfe-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm947xx-cfe-partitions.yaml#
7 title: Broadcom BCM47xx Partitions
12 partitions without any on-flash partition table. On some devices their sizes
15 Discovering partitions on these devices is possible thanks to having a special
19 Most of partitions use ASCII text based magic for determining a type. More
20 complex partitions (like TRX with its HDR0 magic) may include extra header
23 A list of supported partitions includes:
30 As mentioned earlier, role of some partitions may depend on extra
42 const: brcm,bcm947xx-cfe-partitions
48 partitions {
[all …]
|
| D | fixed-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/fixed-partitions.yaml#
7 title: Fixed partitions
14 The partition table should be a node named "partitions". Partitions are then
23 - const: fixed-partitions
25 - const: sercomm,sc-partitions
26 - const: fixed-partitions
72 partitions {
73 compatible = "fixed-partitions";
90 partitions {
91 compatible = "fixed-partitions";
[all …]
|
| D | partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/partitions.yaml#
7 title: Partitions
10 This binding is generic and describes the content of the partitions container
18 - $ref: brcm,bcm4908-partitions.yaml
19 - $ref: brcm,bcm947xx-cfe-partitions.yaml
20 - $ref: fixed-partitions.yaml
21 - $ref: linksys,ns-partitions.yaml
24 - $ref: tplink,safeloader-partitions.yaml
|
| D | brcm,trx.txt | 9 identification fields, CRC32 checksum and the locations of embedded partitions.
10 Its purpose is to store a few partitions in a format that can be distributed as
13 Container can hold up to 4 partitions. The first partition has to contain a
15 executing. Other partitions can be used for operating system purposes. This is
19 partitions have to be less than the 4GiB max size limit.
22 1) v1 which contains 3 partitions
23 2) v2 which contains 4 partitions
39 partitions {
|
| D | brcm,bcm4908-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm4908-partitions.yaml#
10 Broadcom BCM4908 CFE bootloader supports two firmware partitions. One is used
13 This binding allows defining all fixed partitions and marking those containing
24 const: brcm,bcm4908-partitions
48 partitions {
49 compatible = "brcm,bcm4908-partitions";
|
| D | linksys,ns-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/linksys,ns-partitions.yaml#
11 firmware partitions. One is used for regular booting, the other is treated as
14 This binding allows defining all fixed partitions and marking those containing
25 const: linksys,ns-partitions
51 partitions {
52 compatible = "linksys,ns-partitions";
|
| D | qcom,smem-part.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/qcom,smem-part.yaml#
14 Memory (SMEM) based partition table scheme. The maximum partitions supported
15 varies between partition table revisions. V3 supports maximum 16 partitions
16 and V4 supports 48 partitions.
36 partitions {
44 partitions {
|
| D | brcm,bcm963xx-cfe-nor-partitions.txt | 1 Broadcom BCM963XX CFE Loader NOR Flash Partitions
6 NVRAM partition, and the remainder in-between for one to two firmware partitions
12 - compatible : must be "brcm,bcm963xx-cfe-nor-partitions"
21 partitions {
22 compatible = "brcm,bcm963xx-cfe-nor-partitions";
|
| D | nvmem-cells.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/nvmem-cells.yaml#
20 - $ref: /schemas/mtd/partitions/partition.yaml#
35 partitions {
36 compatible = "fixed-partitions";
68 partitions {
69 compatible = "fixed-partitions";
|
| D | seama.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/seama.yaml#
7 title: Seattle Image Partitions
34 partitions {
35 compatible = "fixed-partitions";
|
| D | binman.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/binman.yaml#
21 - $ref: /schemas/mtd/partitions/partition.yaml#
36 partitions {
37 compatible = "fixed-partitions";
|
| D | arm,arm-firmware-suite.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/arm,arm-firmware-suite.yaml#
7 title: ARM Firmware Suite (AFS) Partitions
27 partitions {
|
| D | linux,ubi.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/linux,ubi.yaml#
31 $ref: /schemas/mtd/partitions/ubi-volume.yaml#
42 partitions {
43 compatible = "fixed-partitions";
|
| D | brcm,bcm963xx-imagetag.txt | 5 partitions or non standard bootloader partition sizes. For these a mixed layout
21 partitions {
22 compatible = "fixed-partitions";
|
| D | u-boot.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/u-boot.yaml#
38 partitions {
39 compatible = "fixed-partitions";
|
| D | redboot-fis.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/redboot-fis.yaml#
7 title: RedBoot FLASH Image System (FIS) Partitions
44 partitions {
|
| /Documentation/driver-api/mmc/ |
| D | mmc-dev-parts.rst | 2 SD and MMC Device Partitions
5 Device partitions are additional logical block devices present on the
8 As of this writing, MMC boot partitions as supported and exposed as
12 MMC Boot Partitions
15 Read and write access is provided to the two MMC boot partitions. Due to
30 The boot partitions can also be locked read only until the next power on,
39 The boot partitions can also be locked permanently, but this feature is
|
| /Documentation/devicetree/bindings/mtd/ |
| D | qcom,nandc.yaml | 62 qcom,boot-partitions:
71 partitions by defining first the offset and then the size.
128 qcom,boot-partitions: false
163 qcom,boot-partitions = <0x0 0x58a0000>;
165 partitions {
166 compatible = "fixed-partitions";
205 partitions {
206 compatible = "fixed-partitions";
|
| D | mtd.yaml | 32 partitions:
33 $ref: /schemas/mtd/partitions/partitions.yaml
40 $ref: partitions/partition.yaml
44 $ref: partitions/partition.yaml
|
| D | samsung-s3c2410.txt | 20 Each child device node may optionally contain a 'partitions' sub-node,
40 partitions {
41 compatible = "fixed-partitions";
|
| /Documentation/admin-guide/ |
| D | devices.txt | 119 For partitions, add to the whole disk device number:
126 For Linux/i386, partitions 1-4 are the primary
127 partitions, and 5 and above are logical partitions.
207 Partitions are handled in the same way as for IDE
209 partitions is 15.
509 Partitions are handled the same way as for IDE disks
520 Partitions are handled the same way as for the first
628 Partitions are handled in the same way as for IDE
630 partitions is 15, like SCSI.
716 Partitions are handled the same way as for the first
[all …]
|
| D | ldm.rst | 12 replacement for the MSDOS style partitions. It stores its information in a
14 partitions is limited only by disk space. The maximum number of partitions is
17 Any partitions created under the LDM are called "Dynamic Disks". There are no
18 longer any primary or extended partitions. Normal MSDOS style partitions are
23 partitions and filesystems without the need to reboot.
39 Below we have a 50MiB disk, divided into seven partitions.
66 The LDM Database may not store the partitions in the order that they appear on
103 discovered partitions. However, grub does not understand the LDM partitioning
|
| D | iostats.rst | 12 ``/proc/partitions``. In 2.6 and upper, the same information is found in two
37 On 2.4 you might execute ``grep 'hda ' /proc/partitions``. On 2.6+, you have
129 This counts flush requests executed by disk. Not tracked for partitions.
149 Disks vs Partitions
158 partitions from that for disks. There are only *four* fields available
159 for partitions on 2.6+ machines. This is reflected in the examples above.
178 words, the number of reads for partitions is counted slightly before time
179 of queuing for partitions, and at completion for whole disks. This is
183 reads/writes before merges for partitions and after for disks. Since a
188 In 2.6.25, the full statistic set is again available for partitions and
[all …]
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | u-boot,env.yaml | 74 partitions {
75 compatible = "fixed-partitions";
95 partitions {
96 compatible = "fixed-partitions";
|
12345