Home
last modified time | relevance | path

Searched +full:boot +full:- +full:partitions (Results 1 – 25 of 595) sorted by relevance

12345678910>>...24

/kernel/linux/linux-6.6/Documentation/driver-api/mmc/
Dmmc-dev-parts.rst2 SD and MMC Device Partitions
5 Device partitions are additional logical block devices present on the
8 As of this writing, MMC boot partitions as supported and exposed as
12 MMC Boot Partitions
15 Read and write access is provided to the two MMC boot partitions. Due to
16 the sensitive nature of the boot partition contents, which often store
21 To enable write access to /dev/mmcblkXbootY, disable the forced read-only
26 To re-enable read-only access::
30 The boot partitions can also be locked read only until the next power on,
36 not support boot partition locking, the file will not exist. If the
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/mmc/
Dmmc-dev-parts.rst2 SD and MMC Device Partitions
5 Device partitions are additional logical block devices present on the
8 As of this writing, MMC boot partitions as supported and exposed as
12 MMC Boot Partitions
15 Read and write access is provided to the two MMC boot partitions. Due to
16 the sensitive nature of the boot partition contents, which often store
21 To enable write access to /dev/mmcblkXbootY, disable the forced read-only
26 To re-enable read-only access::
30 The boot partitions can also be locked read only until the next power on,
36 not support boot partition locking, the file will not exist. If the
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/mtd/
Dqcom,nandc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
15 - qcom,ipq806x-nand
16 - qcom,ipq4019-nand
17 - qcom,ipq6018-nand
18 - qcom,ipq8074-nand
19 - qcom,sdx55-nand
26 - description: Core Clock
[all …]
Dingenic,nand.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Paul Cercueil <paul@crapouillou.net>
13 - $ref: nand-controller.yaml#
14 - $ref: /schemas/memory-controllers/ingenic,nemc-peripherals.yaml#
19 - ingenic,jz4740-nand
20 - ingenic,jz4725b-nand
21 - ingenic,jz4780-nand
25 - description: Bank number, offset and size of first attached NAND chip
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/nvmem/
Du-boot,env.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/nvmem/u-boot,env.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: U-Boot environment variables
10 U-Boot uses environment variables to store device parameters and
14 Data is stored using U-Boot specific formats (variant specific header and NUL
15 separated key-value pairs).
30 - Rafał Miłecki <rafal@milecki.pl>
35 - description: A standalone env data block
[all …]
/kernel/linux/linux-6.6/drivers/mtd/parsers/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
11 This provides partitions parser for devices based on BCM47xx
24 tristate "Broadcom's U-Boot partition parser"
27 Broadcom uses a custom way of storing U-Boot environment variables.
28 They are placed inside U-Boot partition itself at unspecified offset.
49 <mtddef> := <mtd-id>:<partdef>[,<partdef>]
51 <mtd-id> := unique id used in mapping driver/device
52 <size> := standard linux memsize OR "-" to denote all
62 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
63 mtdparts=sa1100:-
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/
Dpartition.txt1 Flash partitions in device tree
4 Flash devices can be partitioned into one or more functional ranges (e.g. "boot
8 flash layout set at production time. Some may use on-flash table that describes
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
20 hierarchical (multi-level) layouts and should be used if there is some
21 significant relation between partitions or some partition internally uses
24 Available bindings are listed in the "partitions" subdirectory.
27 Fixed Partitions
30 Partitions can be represented by sub-nodes of a flash device. This can be used
[all …]
Dingenic,nand.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Paul Cercueil <paul@crapouillou.net>
13 - $ref: nand-controller.yaml#
18 - ingenic,jz4740-nand
19 - ingenic,jz4725b-nand
20 - ingenic,jz4780-nand
24 - description: Bank number, offset and size of first attached NAND chip
25 - description: Bank number, offset and size of second attached NAND chip
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/mtd/partitions/
Du-boot.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/u-boot.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: U-Boot bootloader partition
10 U-Boot is a bootlodaer commonly used in embedded devices. It's almost always
17 - Rafał Miłecki <rafal@milecki.pl>
20 - $ref: partition.yaml#
25 - const: brcm,u-boot
27 Broadcom stores environment variables inside a U-Boot partition. They
[all …]
Dfixed-partitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/fixed-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Fixed partitions
12 on-flash partition table such as RedBoot.
14 The partition table should be a node named "partitions". Partitions are then
18 - Rafał Miłecki <rafal@milecki.pl>
23 - const: fixed-partitions
24 - items:
[all …]
Dtplink,safeloader-partitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/tplink,safeloader-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TP-Link SafeLoader partitions
10 TP-Link home routers store various data on flash (e.g. bootloader,
14 Flash space layout of TP-Link devices is stored on flash itself using
15 a custom ASCII-based format. That format was first found in TP-Link
17 CFE and U-Boot bootloaders.
19 Partitions specified in partitions table cover whole flash space. Some
[all …]
/kernel/linux/linux-5.10/include/linux/platform_data/
Dmtd-nand-s3c2410.h1 /* SPDX-License-Identifier: GPL-2.0-only */
6 * S3C2410 - NAND device controller platform_device info
15 * struct s3c2410_nand_set - define a set of one or more nand chips
16 * @flash_bbt: Openmoko u-boot can create a Bad Block Table
18 * look for it at boot time and also skip the NAND
22 * @nr_partitions: Number of partitions pointed to by @partitions
24 * @nr_map: Map for low-layer logical to physical chip numbers (option)
25 * @partitions: The mtd partition list
29 * a warning at boot time.
39 struct mtd_partition *partitions; member
[all …]
/kernel/linux/linux-6.6/include/linux/platform_data/
Dmtd-nand-s3c2410.h1 /* SPDX-License-Identifier: GPL-2.0-only */
6 * S3C2410 - NAND device controller platform_device info
15 * struct s3c2410_nand_set - define a set of one or more nand chips
16 * @flash_bbt: Openmoko u-boot can create a Bad Block Table
18 * look for it at boot time and also skip the NAND
22 * @nr_partitions: Number of partitions pointed to by @partitions
24 * @nr_map: Map for low-layer logical to physical chip numbers (option)
25 * @partitions: The mtd partition list
29 * a warning at boot time.
39 struct mtd_partition *partitions; member
[all …]
/kernel/linux/linux-6.6/arch/arm/boot/dts/aspeed/
Dopenbmc-flash-layout.dtsi1 // SPDX-License-Identifier: GPL-2.0+
3 partitions {
4 compatible = "fixed-partitions";
5 #address-cells = <1>;
6 #size-cells = <1>;
8 u-boot@0 {
10 label = "u-boot";
13 u-boot-env@60000 {
15 label = "u-boot-env";
Dopenbmc-flash-layout-128.dtsi1 // SPDX-License-Identifier: GPL-2.0+
3 partitions {
4 compatible = "fixed-partitions";
5 #address-cells = <1>;
6 #size-cells = <1>;
8 u-boot@0 {
10 label = "u-boot";
13 u-boot-env@e0000 {
15 label = "u-boot-env";
Dopenbmc-flash-layout-64.dtsi1 // SPDX-License-Identifier: GPL-2.0+
6 partitions {
7 compatible = "fixed-partitions";
8 #address-cells = <1>;
9 #size-cells = <1>;
11 u-boot@0 {
13 label = "u-boot";
16 u-boot-env@e0000 {
18 label = "u-boot-env";
Dopenbmc-flash-layout-64-alt.dtsi1 // SPDX-License-Identifier: GPL-2.0+
6 partitions {
7 compatible = "fixed-partitions";
8 #address-cells = <1>;
9 #size-cells = <1>;
11 u-boot@0 {
13 label = "alt-u-boot";
16 u-boot-env@e0000 {
18 label = "alt-u-boot-env";
23 label = "alt-kernel";
[all …]
Dfacebook-bmc-flash-layout-128.dtsi1 // SPDX-License-Identifier: GPL-2.0+
4 partitions {
5 compatible = "fixed-partitions";
6 #address-cells = <1>;
7 #size-cells = <1>;
10 * u-boot partition: 896KB.
12 u-boot@0 {
14 label = "u-boot";
18 * u-boot environment variables: 64KB.
20 u-boot-env@e0000 {
[all …]
Dfacebook-bmc-flash-layout.dtsi1 // SPDX-License-Identifier: GPL-2.0+
4 partitions {
5 compatible = "fixed-partitions";
6 #address-cells = <1>;
7 #size-cells = <1>;
9 u-boot@0 {
11 label = "u-boot";
14 u-boot-env@60000 {
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dopenbmc-flash-layout.dtsi1 // SPDX-License-Identifier: GPL-2.0+
3 partitions {
4 compatible = "fixed-partitions";
5 #address-cells = <1>;
6 #size-cells = <1>;
8 u-boot@0 {
10 label = "u-boot";
13 u-boot-env@60000 {
15 label = "u-boot-env";
Dopenbmc-flash-layout-128.dtsi1 // SPDX-License-Identifier: GPL-2.0+
3 partitions {
4 compatible = "fixed-partitions";
5 #address-cells = <1>;
6 #size-cells = <1>;
8 u-boot@0 {
10 label = "u-boot";
13 u-boot-env@e0000 {
15 label = "u-boot-env";
Dfacebook-bmc-flash-layout.dtsi1 // SPDX-License-Identifier: GPL-2.0+
4 partitions {
5 compatible = "fixed-partitions";
6 #address-cells = <1>;
7 #size-cells = <1>;
9 u-boot@0 {
11 label = "u-boot";
14 u-boot-env@60000 {
Dam335x-moxa-uc-2100-common.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2018 MOXA Inc. - https://www.moxa.com/
13 vbat: vbat-regulator {
14 compatible = "regulator-fixed";
18 vmmcsd_fixed: vmmcsd-regulator {
19 compatible = "regulator-fixed";
20 regulator-name = "vmmcsd_fixed";
21 regulator-min-microvolt = <3300000>;
22 regulator-max-microvolt = <3300000>;
23 regulator-boot-on;
[all …]
Darmada-390-db.dts1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
4 * (DB-88F6920)
11 /dts-v1/;
12 #include "armada-390.dtsi"
16 compatible = "marvell,a390-db", "marvell,armada390";
19 stdout-path = "serial0:115200n8";
31 internal-regs {
34 clock-frequency = <100000>;
81 pinctrl-0 = <&spi1_pins>;
82 pinctrl-names = "default";
[all …]
/kernel/linux/linux-6.6/arch/arm/boot/dts/ti/omap/
Dam335x-moxa-uc-2100-common.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2018 MOXA Inc. - https://www.moxa.com/
13 vbat: vbat-regulator {
14 compatible = "regulator-fixed";
18 vmmcsd_fixed: vmmcsd-regulator {
19 compatible = "regulator-fixed";
20 regulator-name = "vmmcsd_fixed";
21 regulator-min-microvolt = <3300000>;
22 regulator-max-microvolt = <3300000>;
23 regulator-boot-on;
[all …]

12345678910>>...24