| /linux/Documentation/devicetree/bindings/mtd/partitions/ |
| H 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 {
|
| H 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";
|
| H 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/drivers/mtd/parsers/ |
| H A D | Kconfig | 6 This provides partitions parser for devices based on BCM47xx
60 Same flash, but 2 named partitions, the first one being read-only:
80 This provides partitions parser for BCM4908 family devices
81 that can have multiple "firmware" partitions. It takes care of
89 This provides partitions parser for Linksys devices based on Broadcom
91 two "firmware" partitions. Currently used firmware has to be detected
95 tristate "Parser for BCM963XX Image Tag format partitions"
101 and rootfs partitions.
103 header and creates up to two partitions, kernel and rootfs.
114 register MTD 'partitions' corresponding to each image detected,
[all …]
|
| /linux/Documentation/admin-guide/ |
| H 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
|
| H A 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.
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
206 appear in both ``/proc/partitions`` and ``/proc/stat``, although the ones in
[all …]
|
| /linux/Documentation/driver-api/mmc/ |
| H 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/marvell/ |
| H A D | armada-390-db.dts | 92 partitions {
93 compatible = "fixed-partitions";
123 partitions {
124 compatible = "fixed-partitions";
|
| H A D | armada-385-db-88f6820-amc.dts | 103 partitions {
104 compatible = "fixed-partitions";
137 partitions {
138 compatible = "fixed-partitions";
|
| /linux/arch/arm/boot/dts/ti/omap/ |
| H A D | am335x-moxa-uc-2100-common.dtsi | 191 partitions {
192 compatible = "fixed-partitions";
197 partitions@0 {
202 partitions@1 {
207 partitions@2 {
|
| /linux/fs/nls/ |
| H A 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 …]
|
| /linux/fs/ufs/ |
| H A D | Kconfig | 9 Unixes can create and mount hard disk partitions and diskettes using
11 these partitions; if you also want to write to them, say Y to the
36 Say Y here if you want to try writing to UFS partitions. This is
37 experimental, so you should back up your UFS partitions beforehand.
|
| /linux/arch/arm/boot/dts/qcom/ |
| H A D | qcom-ipq4018-jalapeno.dts | 78 partitions {
79 compatible = "fixed-partitions";
139 partitions {
140 compatible = "fixed-partitions";
|
| H A D | qcom-ipq4018-ap120c-ac.dtsi | 119 partitions {
120 compatible = "fixed-partitions";
204 partitions {
205 compatible = "fixed-partitions";
|
| /linux/drivers/mtd/maps/ |
| H 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()
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| H A D | samsung-s3c2410.txt | 20 Each child device node may optionally contain a 'partitions' sub-node,
40 partitions {
41 compatible = "fixed-partitions";
|
| /linux/arch/arm/boot/dts/broadcom/ |
| H A D | bcm5301x-nand-cs0.dtsi | 16 partitions {
17 compatible = "brcm,bcm947xx-cfe-partitions";
|
| H A D | bcm53016-meraki-mr32.dts | 128 partitions {
132 * [ 1.721667] 1 bcm47xxpart partitions found on MTD device brcmnand.0
133 * [ 1.727962] Creating 1 MTD partitions on "brcmnand.0":
137 compatible = "fixed-partitions";
|
| H A D | bcm47081-tplink-archer-c5-v2.dts | 97 partitions {
98 compatible = "tplink,safeloader-partitions";
99 partitions-table-offset = <0xe50000>;
|
| H A D | bcm4709-tplink-archer-c9-v1.dts | 106 partitions {
107 compatible = "tplink,safeloader-partitions";
108 partitions-table-offset = <0xe50000>;
|
| /linux/arch/mips/boot/dts/brcm/ |
| H A D | bcm97xxx-nand-cs1-bch24.dtsi | 12 partitions {
13 compatible = "fixed-partitions";
|
| H A D | bcm97xxx-nand-cs1-bch4.dtsi | 12 partitions {
13 compatible = "fixed-partitions";
|
| /linux/arch/arm/boot/dts/aspeed/ |
| H A D | openbmc-flash-layout.dtsi | 3 partitions {
4 compatible = "fixed-partitions";
|
| H A D | openbmc-flash-layout-128.dtsi | 3 partitions {
4 compatible = "fixed-partitions";
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | unstriped.rst | 97 neighbor environments. When two partitions are created on the
99 can affect writes on another partition. This is because the partitions
101 and make partitions on each new exposed device the two partitions are now
106 when we run the test on a combined drive with partitions, we were able
|