/linux/Documentation/devicetree/bindings/mtd/partitions/ |
A D | fixed-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/fixed-partitions.yaml# 7 title: Fixed partitions 22 const: fixed-partitions 40 partitions { 41 compatible = "fixed-partitions"; 56 partitions { 57 compatible = "fixed-partitions"; 68 partitions { 69 compatible = "fixed-partitions"; 86 partitions { [all …]
|
A D | brcm,bcm947xx-cfe-partitions.txt | 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" 39 partitions { [all …]
|
A 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 22 const: brcm,bcm4908-partitions 46 partitions { 47 compatible = "brcm,bcm4908-partitions";
|
A 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 {
|
A 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 23 const: linksys,ns-partitions 49 partitions { 50 compatible = "linksys,ns-partitions";
|
A 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. 30 partitions {
|
A D | nvmem-cells.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/nvmem-cells.yaml# 33 partitions { 34 compatible = "fixed-partitions"; 66 partitions { 67 compatible = "fixed-partitions";
|
A D | brcm,bcm963xx-cfe-nor-partitions.txt | 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";
|
A D | brcm,bcm963xx-imagetag.txt | 5 partitions or non standard bootloader partition sizes. For these a mixed layout 21 partitions { 22 compatible = "fixed-partitions";
|
/linux/block/partitions/ |
A D | .built-in.a.cmd | 1 …partitions/built-in.a := echo >/dev/null; rm -f block/partitions/built-in.a; /usr/bin/ccache /home…
|
/linux/Documentation/devicetree/bindings/mtd/ |
A 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 Deprecated: partitions defined in flash node 30 For backwards compatibility partitions as direct subnodes of the flash device are 33 string are not considered partitions, as they may be used for other bindings.
|
A D | ingenic,nand.yaml | 32 partitions: 35 Node containing description of fixed partitions. 102 partitions { 103 compatible = "fixed-partitions";
|
A D | samsung-s3c2410.txt | 20 Each child device node may optionally contain a 'partitions' sub-node, 40 partitions { 41 compatible = "fixed-partitions";
|
/linux/drivers/mtd/parsers/ |
A 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: 75 This provides partitions parser for BCM4908 family devices 76 that can have multiple "firmware" partitions. It takes care of 90 tristate "Parser for BCM963XX Image Tag format partitions" 96 and rootfs partitions. 98 header and creates up to two partitions, kernel and rootfs. 109 register MTD 'partitions' corresponding to each image detected, 117 tristate "Parser for TRX format partitions" 121 may contain up to 3/4 partitions (depending on the version). [all …]
|
/linux/Documentation/admin-guide/ |
A 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
|
/linux/Documentation/driver-api/mmc/ |
A D | mmc-dev-parts.rst | 5 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/arch/arm/boot/dts/ |
A D | armada-390-db.dts | 92 partitions { 93 compatible = "fixed-partitions"; 123 partitions { 124 compatible = "fixed-partitions";
|
A D | armada-385-db-88f6820-amc.dts | 103 partitions { 104 compatible = "fixed-partitions"; 137 partitions { 138 compatible = "fixed-partitions";
|
A D | am335x-moxa-uc-2100-common.dtsi | 193 partitions { 194 compatible = "fixed-partitions"; 199 partitions@0 { 204 partitions@1 { 209 partitions@2 {
|
A D | qcom-ipq4018-jalapeno.dts | 83 partitions { 84 compatible = "fixed-partitions"; 144 partitions { 145 compatible = "fixed-partitions";
|
/linux/fs/nls/ |
A D | Kconfig | 463 Mac partitions correctly. This does apply to the filenames 478 Mac partitions correctly. This does apply to the filenames 492 Mac partitions correctly. This does apply to the filenames 506 Mac partitions correctly. This does apply to the filenames 520 Mac partitions correctly. This does apply to the filenames 534 Mac partitions correctly. This does apply to the filenames 548 Mac partitions correctly. This does apply to the filenames 562 Mac partitions correctly. This does apply to the filenames 576 Mac partitions correctly. This does apply to the filenames 590 Mac partitions correctly. This does apply to the filenames [all …]
|
/linux/arch/arm64/boot/dts/marvell/ |
A D | armada-7040-db.dts | 91 partitions { 92 compatible = "fixed-partitions"; 162 partitions { 163 compatible = "fixed-partitions"; 194 partitions { 195 compatible = "fixed-partitions";
|
/linux/block/ |
A D | built-in.a | 27 partitions/core.o/ 28 partitions/msdos.o/ 29 partitions/efi.o/
|
/linux/fs/ufs/ |
A D | Kconfig | 8 Unixes can create and mount hard disk partitions and diskettes using 10 these partitions; if you also want to write to them, say Y to the 35 Say Y here if you want to try writing to UFS partitions. This is 36 experimental, so you should back up your UFS partitions beforehand.
|
/linux/drivers/mtd/maps/ |
A D | impa7.c | 47 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()
|