Searched refs:partitions (Results 1 – 25 of 359) sorted by relevance
12345678910>>...15
| /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.
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";
|
| /kernel/linux/linux-5.10/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 {
|
| 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";
|
| D | brcm,bcm963xx-imagetag.txt | 5 partitions or non standard bootloader partition sizes. For these a mixed layout
21 partitions {
22 compatible = "fixed-partitions";
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/driver-api/mmc/ |
| 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
|
| /kernel/linux/linux-5.10/drivers/mtd/parsers/ |
| 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-5.10/arch/arm/boot/dts/ |
| D | armada-390-db.dts | 92 partitions {
93 compatible = "fixed-partitions";
123 partitions {
124 compatible = "fixed-partitions";
|
| D | armada-385-db-88f6820-amc.dts | 103 partitions {
104 compatible = "fixed-partitions";
137 partitions {
138 compatible = "fixed-partitions";
|
| D | am335x-moxa-uc-2100-common.dtsi | 193 partitions {
194 compatible = "fixed-partitions";
199 partitions@0 {
204 partitions@1 {
209 partitions@2 {
|
| D | bcm5301x-nand-cs0.dtsi | 16 partitions {
17 compatible = "brcm,bcm947xx-cfe-partitions";
|
| D | openbmc-flash-layout.dtsi | 3 partitions {
4 compatible = "fixed-partitions";
|
| D | openbmc-flash-layout-128.dtsi | 3 partitions {
4 compatible = "fixed-partitions";
|
| D | bcm53016-meraki-mr32.dts | 155 partitions {
159 * [ 1.721667] 1 bcm47xxpart partitions found on MTD device brcmnand.0
160 * [ 1.727962] Creating 1 MTD partitions on "brcmnand.0":
164 compatible = "fixed-partitions";
|
| D | armada-385-linksys-shelby.dts | 76 partitions {
77 compatible = "fixed-partitions";
136 * partitions would break the bootloader
|
| /kernel/linux/linux-5.10/drivers/mtd/maps/ |
| 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()
|
| /kernel/linux/linux-5.10/fs/ufs/ |
| 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.
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/marvell/ |
| D | armada-7040-db.dts | 91 partitions {
92 compatible = "fixed-partitions";
162 partitions {
163 compatible = "fixed-partitions";
194 partitions {
195 compatible = "fixed-partitions";
|
| D | armada-8040-db.dts | 80 partitions {
81 compatible = "fixed-partitions";
238 partitions {
239 compatible = "fixed-partitions";
274 partitions {
275 compatible = "fixed-partitions";
|
| /kernel/linux/linux-5.10/arch/mips/boot/dts/brcm/ |
| D | bcm97xxx-nand-cs1-bch4.dtsi | 12 partitions {
13 compatible = "fixed-partitions";
|
| D | bcm97xxx-nand-cs1-bch24.dtsi | 12 partitions {
13 compatible = "fixed-partitions";
|
| /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 …]
|
12345678910>>...15