| /Linux-v4.19/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.
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.
40 For backwards compatibility partitions as direct subnodes of the flash device are
43 string are not considered partitions, as they may be used for other bindings.
[all …]
|
| D | samsung-s3c2410.txt | 20 Each child device node may optionally contain a 'partitions' sub-node,
40 partitions {
41 compatible = "fixed-partitions";
|
| D | qcom_nandc.txt | 55 Each nandcs device node may optionally contain a 'partitions' sub-node, which
83 partitions {
84 compatible = "fixed-partitions";
122 partitions {
123 compatible = "fixed-partitions";
|
| /Linux-v4.19/Documentation/devicetree/bindings/mtd/partitions/ |
| 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 …]
|
| 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 {
|
| /Linux-v4.19/Documentation/ |
| D | ldm.txt | 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.txt | 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
141 partitions from that for disks. There are only *four* fields available
142 for partitions on 2.6+ machines. This is reflected in the examples above.
161 words, the number of reads for partitions is counted slightly before time
162 of queuing for partitions, and at completion for whole disks. This is
166 reads/writes before merges for partitions and after for disks. Since a
171 In 2.6.25, the full statistic set is again available for partitions and
189 appear in both ``/proc/partitions`` and ``/proc/stat``, although the ones in
190 ``/proc/stat`` take a very different format from those in ``/proc/partitions``
|
| /Linux-v4.19/Documentation/mmc/ |
| D | mmc-dev-parts.txt | 4 Device partitions are additional logical block devices present on the
7 As of this writing, MMC boot partitions as supported and exposed as
14 Read and write access is provided to the two MMC boot partitions. Due to
29 The boot partitions can also be locked read only until the next power on,
38 The boot partitions can also be locked permanently, but this feature is
|
| /Linux-v4.19/drivers/mtd/parsers/ |
| D | Kconfig | 2 tristate "Parser for TRX format partitions"
6 may contain up to 3/4 partitions (depending on the version).
7 This driver will parse TRX header and report at least two partitions:
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | armada-390-db.dts | 92 partitions {
93 compatible = "fixed-partitions";
123 partitions {
124 compatible = "fixed-partitions";
|
| D | openbmc-flash-layout.dtsi | 3 partitions {
4 compatible = "fixed-partitions";
|
| D | armada-385-linksys-caiman.dts | 76 partitions {
77 compatible = "fixed-partitions";
136 * partitions would break the bootloader
|
| D | armada-385-linksys-cobra.dts | 76 partitions {
77 compatible = "fixed-partitions";
136 * partitions would break the bootloader
|
| D | armada-385-linksys-shelby.dts | 76 partitions {
77 compatible = "fixed-partitions";
136 * partitions would break the bootloader
|
| /Linux-v4.19/arch/arm64/boot/dts/marvell/ |
| D | armada-7040-db.dts | 75 partitions {
76 compatible = "fixed-partitions";
144 partitions {
145 compatible = "fixed-partitions";
178 partitions {
179 compatible = "fixed-partitions";
|
| D | armada-8040-db.dts | 90 partitions {
91 compatible = "fixed-partitions";
223 partitions {
224 compatible = "fixed-partitions";
259 partitions {
260 compatible = "fixed-partitions";
|
| /Linux-v4.19/drivers/mtd/maps/ |
| D | impa7.c | 50 static const struct mtd_partition partitions[] = variable
91 mtd_device_register(impa7_mtd[i], partitions, in init_impa7()
92 ARRAY_SIZE(partitions)); in init_impa7()
|
| /Linux-v4.19/fs/ufs/ |
| D | Kconfig | 7 Unixes can create and mount hard disk partitions and diskettes using
9 these partitions; if you also want to write to them, say Y to the
34 Say Y here if you want to try writing to UFS partitions. This is
35 experimental, so you should back up your UFS partitions beforehand.
|
| /Linux-v4.19/arch/mips/boot/dts/brcm/ |
| D | bcm97xxx-nand-cs1-bch24.dtsi | 12 partitions {
13 compatible = "fixed-partitions";
|
| D | bcm97xxx-nand-cs1-bch4.dtsi | 12 partitions {
13 compatible = "fixed-partitions";
|
| /Linux-v4.19/fs/nls/ |
| D | Kconfig | 46 DOS/Windows partitions correctly. This does apply to the filenames
58 DOS/Windows partitions correctly. This does apply to the filenames
70 DOS/Windows partitions correctly. This does apply to the filenames
83 DOS/Windows partitions correctly. This does apply to the filenames
99 DOS/Windows partitions correctly. This does apply to the filenames
114 DOS/Windows partitions correctly. This does apply to the filenames
125 DOS/Windows partitions correctly. This does apply to the filenames
136 DOS/Windows partitions correctly. This does apply to the filenames
147 DOS/Windows partitions correctly. This does apply to the filenames
158 DOS/Windows partitions correctly. This does apply to the filenames
[all …]
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | unstriped.txt | 93 neighbor environments. When two partitions are created on the
95 can affect writes on another partition. This is because the partitions
97 and make partitions on each new exposed device the two partitions are now
102 when we run the test on a combined drive with partitions, we were able
|
| /Linux-v4.19/arch/arm/mach-s3c24xx/ |
| D | mach-anubis.c | 178 .partitions = anubis_default_nand_part,
185 .partitions = anubis_default_nand_part,
192 .partitions = anubis_default_nand_part,
394 anubis_nand_sets[0].partitions = anubis_default_nand_part_large; in anubis_map_io()
|
| D | mach-osiris.c | 193 .partitions = osiris_default_nand_part,
200 .partitions = osiris_default_nand_part,
208 .partitions = osiris_default_nand_part,
369 osiris_nand_sets[0].partitions = osiris_default_nand_part_large; in osiris_map_io()
|
| /Linux-v4.19/drivers/mtd/ |
| D | cmdlinepart.c | 80 static struct cmdline_mtd_partition *partitions; variable
280 this_mtd->next = partitions; in mtdpart_setup_real()
281 partitions = this_mtd; in mtdpart_setup_real()
329 for (part = partitions; part; part = part->next) { in parse_cmdline_partitions()
|
