Home
last modified time | relevance | path

Searched refs:partitions (Results 1 – 25 of 483) sorted by relevance

12345678910>>...20

/linux/Documentation/devicetree/bindings/mtd/partitions/
A Dfixed-partitions.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/fixed-partitions.yaml#
7 title: Fixed partitions
23 - const: fixed-partitions
25 - const: sercomm,sc-partitions
26 - const: fixed-partitions
72 partitions {
90 partitions {
104 partitions {
123 partitions {
161 partitions {
[all …]
A Dtplink,safeloader-partitions.yaml4 $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).
33 const: tplink,safeloader-partitions
35 partitions-table-offset:
36 description: Flash offset of partitions table
44 - partitions-table-offset
50 partitions {
51 compatible = "tplink,safeloader-partitions";
[all …]
A Dpartitions.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/partitions.yaml#
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
A Dbrcm,bcm947xx-cfe-partitions.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm947xx-cfe-partitions.yaml#
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 {
49 compatible = "brcm,bcm947xx-cfe-partitions";
A Dbrcm,bcm4908-partitions.yaml4 $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";
A Dbrcm,trx.txt9 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 {
A Dlinksys,ns-partitions.yaml4 $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";
A Dqcom,smem-part.yaml4 $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 {
A Dnvmem-cells.yaml4 $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";
A Dbrcm,bcm963xx-cfe-nor-partitions.txt6 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";
A Dbinman.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/binman.yaml#
21 - $ref: /schemas/mtd/partitions/partition.yaml#
36 partitions {
37 compatible = "fixed-partitions";
A Dlinux,ubi.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/linux,ubi.yaml#
31 $ref: /schemas/mtd/partitions/ubi-volume.yaml#
42 partitions {
43 compatible = "fixed-partitions";
A Dbrcm,bcm963xx-imagetag.txt5 partitions or non standard bootloader partition sizes. For these a mixed layout
21 partitions {
22 compatible = "fixed-partitions";
A Dseama.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/seama.yaml#
34 partitions {
35 compatible = "fixed-partitions";
A Du-boot.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/u-boot.yaml#
38 partitions {
39 compatible = "fixed-partitions";
/linux/drivers/mtd/parsers/
A DKconfig6 This provides partitions parser for devices based on BCM47xx
80 This provides partitions parser for BCM4908 family devices
81 that can have multiple "firmware" partitions. It takes care of
95 tristate "Parser for BCM963XX Image Tag format partitions"
101 and rootfs partitions.
103 header and creates up to two partitions, kernel and rootfs.
122 tristate "TP-Link Safeloader partitions parser"
133 This driver reads partitions table, parses it and creates MTD
134 partitions.
137 tristate "Parser for TRX format partitions"
[all …]
/linux/Documentation/admin-guide/
A Dldm.rst12 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
/linux/Documentation/driver-api/mmc/
A Dmmc-dev-parts.rst5 Device partitions are additional logical block devices present on the
8 As of this writing, MMC boot partitions as supported and exposed as
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
/linux/Documentation/devicetree/bindings/mtd/
A Dqcom,nandc.yaml62 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";
A Dmtd.yaml32 partitions:
33 $ref: /schemas/mtd/partitions/partitions.yaml
40 $ref: partitions/partition.yaml
44 $ref: partitions/partition.yaml
/linux/arch/arm/boot/dts/renesas/
A Dr7s72100-genmai.dts44 partitions {
45 compatible = "fixed-partitions";
120 partitions {
121 compatible = "fixed-partitions";
147 partitions {
148 compatible = "fixed-partitions";
/linux/drivers/media/pci/mgb4/
A Dmgb4_core.c219 mgbdev->partitions[0].name = mgbdev->fw_part_name; in init_spi()
221 mgbdev->partitions[0].size = 0x950000; in init_spi()
222 mgbdev->partitions[0].offset = 0x1000000; in init_spi()
224 mgbdev->partitions[0].size = 0x400000; in init_spi()
225 mgbdev->partitions[0].offset = 0x400000; in init_spi()
227 mgbdev->partitions[0].mask_flags = 0; in init_spi()
231 mgbdev->partitions[1].name = mgbdev->data_part_name; in init_spi()
232 mgbdev->partitions[1].size = 0x10000; in init_spi()
233 mgbdev->partitions[1].offset = 0xFF0000; in init_spi()
234 mgbdev->partitions[1].mask_flags = MTD_CAP_NORFLASH; in init_spi()
[all …]
/linux/arch/arm/boot/dts/marvell/
A Darmada-390-db.dts92 partitions {
93 compatible = "fixed-partitions";
123 partitions {
124 compatible = "fixed-partitions";
A Darmada-385-db-88f6820-amc.dts103 partitions {
104 compatible = "fixed-partitions";
137 partitions {
138 compatible = "fixed-partitions";
/linux/drivers/mtd/maps/
A Dimpa7.c47 static const struct mtd_partition partitions[] = variable
88 mtd_device_register(impa7_mtd[i], partitions, in init_impa7()
89 ARRAY_SIZE(partitions)); in init_impa7()

Completed in 28 milliseconds

12345678910>>...20