| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 1 Flash partitions in device tree
12 To assist system software in locating partitions, we allow describing which
14 a subnode of the flash device that is named 'partitions'. It must have a
21 significant relation between partitions or some partition internally uses
24 Available bindings are listed in the "partitions" subdirectory.
27 Fixed Partitions
30 Partitions can be represented by sub-nodes of a flash device. This can be used
36 'partitions'. This node should have the following property:
37 - compatible : (required) must be "fixed-partitions"
38 Partitions are then defined in subnodes of the partitions node.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mtd/partitions/ |
| 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
54 partitions {
55 compatible = "fixed-partitions";
71 partitions {
72 compatible = "fixed-partitions";
[all …]
|
| 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 | 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";
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm947xx-cfe-partitions.txt | 1 Broadcom BCM47xx Partitions
5 home routers. Their BCM947xx boards using CFE bootloader have several partitions
9 Discovering partitions on these devices is possible thanks to having a special
13 Most of partitions use ASCII text based magic for determining a type. More
14 complex partitions (like TRX with its HDR0 magic) may include extra header
17 A list of supported partitions includes:
24 As mentioned earlier, role of some partitions may depend on extra configuration.
30 Devices using Broadcom partitions described above should should have flash node
31 with a subnode named "partitions" using following properties:
34 - compatible : (required) must be "brcm,bcm947xx-cfe-partitions"
[all …]
|
| 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
34 partitions {
|
| /kernel/linux/linux-6.6/drivers/mtd/parsers/ |
| D | Kconfig | 11 This provides partitions parser for devices based on BCM47xx
65 Same flash, but 2 named partitions, the first one being read-only:
85 This provides partitions parser for BCM4908 family devices
86 that can have multiple "firmware" partitions. It takes care of
94 This provides partitions parser for Linksys devices based on Broadcom
96 two "firmware" partitions. Currently used firmware has to be detected
100 tristate "Parser for BCM963XX Image Tag format partitions"
106 and rootfs partitions.
108 header and creates up to two partitions, kernel and rootfs.
119 register MTD 'partitions' corresponding to each image detected,
[all …]
|
| D | ofpart_core.c | 3 * Flash partitions described by the OF (or flattened) device tree
17 #include <linux/mtd/partitions.h>
61 ofpart_node = of_get_child_by_name(mtd_node, "partitions"); in parse_fixed_partitions()
68 …pr_debug("%s: 'partitions' subnode not found on %pOF. Trying to parse direct subnodes as partition… in parse_fixed_partitions()
79 /* The 'partitions' subnode might be used by another parser */ in parse_fixed_partitions()
129 * partitions as direct children of the nand controller. in parse_fixed_partitions()
132 * U-Boot) just add the partitions there assuming in parse_fixed_partitions()
140 …t partition %pOF (%pOF) #size-cells is wrongly set to <0>, assuming <1> for parsing partitions.\n", in parse_fixed_partitions()
193 { .compatible = "fixed-partitions" },
195 { .compatible = "brcm,bcm4908-partitions", .data = &bcm4908_partitions_quirks, },
[all …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/drivers/mtd/parsers/ |
| D | ofpart.c | 3 * Flash partitions described by the OF (or flattened) device tree
17 #include <linux/mtd/partitions.h>
42 ofpart_node = of_get_child_by_name(mtd_node, "partitions"); in parse_fixed_partitions()
49 …pr_debug("%s: 'partitions' subnode not found on %pOF. Trying to parse direct subnodes as partition… in parse_fixed_partitions()
53 } else if (!of_device_is_compatible(ofpart_node, "fixed-partitions")) { in parse_fixed_partitions()
54 /* The 'partitions' subnode might be used by another parser */ in parse_fixed_partitions()
143 { .compatible = "fixed-partitions" },
150 .name = "fixed-partitions",
171 part = of_get_property(dp, "partitions", &plen); in parse_ofoldpart_partitions()
173 return 0; /* No partitions found */ in parse_ofoldpart_partitions()
[all …]
|
| D | Kconfig | 11 This provides partitions parser for devices based on BCM47xx
55 Same flash, but 2 named partitions, the first one being read-only:
71 tristate "Parser for BCM963XX Image Tag format partitions"
77 and rootfs partitions.
79 header and creates up to two partitions, kernel and rootfs.
90 register MTD 'partitions' corresponding to each image detected,
98 tristate "Parser for TRX format partitions"
102 may contain up to 3/4 partitions (depending on the version).
103 This driver will parse TRX header and report at least two partitions:
124 MTD 'partitions' corresponding to each image in the table, enable
|
| /kernel/linux/linux-6.6/fs/nls/ |
| D | Kconfig | 47 DOS/Windows partitions correctly. This does apply to the filenames
59 DOS/Windows partitions correctly. This does apply to the filenames
71 DOS/Windows partitions correctly. This does apply to the filenames
84 DOS/Windows partitions correctly. This does apply to the filenames
100 DOS/Windows partitions correctly. This does apply to the filenames
115 DOS/Windows partitions correctly. This does apply to the filenames
126 DOS/Windows partitions correctly. This does apply to the filenames
137 DOS/Windows partitions correctly. This does apply to the filenames
148 DOS/Windows partitions correctly. This does apply to the filenames
159 DOS/Windows partitions correctly. This does apply to the filenames
[all …]
|
| /kernel/linux/linux-5.10/fs/nls/ |
| D | Kconfig | 47 DOS/Windows partitions correctly. This does apply to the filenames
59 DOS/Windows partitions correctly. This does apply to the filenames
71 DOS/Windows partitions correctly. This does apply to the filenames
84 DOS/Windows partitions correctly. This does apply to the filenames
100 DOS/Windows partitions correctly. This does apply to the filenames
115 DOS/Windows partitions correctly. This does apply to the filenames
126 DOS/Windows partitions correctly. This does apply to the filenames
137 DOS/Windows partitions correctly. This does apply to the filenames
148 DOS/Windows partitions correctly. This does apply to the filenames
159 DOS/Windows partitions correctly. This does apply to the filenames
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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.
519 Partitions are handled the same way as for IDE disks
530 Partitions are handled the same way as for the first
638 Partitions are handled in the same way as for IDE
640 partitions is 15, like SCSI.
726 Partitions are handled the same way as for the first
[all …]
|
| /kernel/linux/linux-5.10/drivers/mtd/ |
| D | mtdpart.c | 17 #include <linux/mtd/partitions.h>
52 printk(KERN_ERR"memory allocation error while creating partitions for \"%s\"\n", in allocate_partition()
75 * concern for showing the same data in multiple partitions. in allocate_partition()
80 * distinguish between the parent and its partitions in sysfs. in allocate_partition()
87 INIT_LIST_HEAD(&child->partitions); in allocate_partition()
270 list_add_tail(&child->part.node, &parent->partitions); in mtd_add_partition()
297 * This function must be called with the partitions mutex locked.
304 list_for_each_entry_safe(child, next, &mtd->partitions, part.node) { in __mtd_del_partition()
332 list_for_each_entry_safe(child, next, &mtd->partitions, part.node) { in __del_mtd_partitions()
357 pr_info("Deleting MTD partitions on \"%s\":\n", mtd->name); in del_mtd_partitions()
[all …]
|
| /kernel/linux/linux-6.6/drivers/mtd/ |
| D | mtdpart.c | 17 #include <linux/mtd/partitions.h>
59 printk(KERN_ERR"memory allocation error while creating partitions for \"%s\"\n", in allocate_partition()
82 * concern for showing the same data in multiple partitions. in allocate_partition()
87 * distinguish between the parent and its partitions in sysfs. in allocate_partition()
94 INIT_LIST_HEAD(&child->partitions); in allocate_partition()
276 list_add_tail(&child->part.node, &parent->partitions); in mtd_add_partition()
303 * This function must be called with the partitions mutex locked.
310 list_for_each_entry_safe(child, next, &mtd->partitions, part.node) { in __mtd_del_partition()
335 list_for_each_entry_safe(child, next, &mtd->partitions, part.node) { in __del_mtd_partitions()
358 pr_info("Deleting MTD partitions on \"%s\":\n", mtd->name); in del_mtd_partitions()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mtd/ |
| D | qcom,nandc.yaml | 50 qcom,boot-partitions:
59 partitions by defining first the offset and then the size.
133 qcom,boot-partitions: true
138 qcom,boot-partitions: false
173 qcom,boot-partitions = <0x0 0x58a0000>;
175 partitions {
176 compatible = "fixed-partitions";
215 partitions {
216 compatible = "fixed-partitions";
|