Home
last modified time | relevance | path

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

12345678910>>...14

/linux-6.14.4/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 …]
/linux-6.14.4/drivers/mtd/parsers/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
6 This provides partitions parser for devices based on BCM47xx
19 tristate "Broadcom's U-Boot partition parser"
22 Broadcom uses a custom way of storing U-Boot environment variables.
23 They are placed inside U-Boot partition itself at unspecified offset.
44 <mtddef> := <mtd-id>:<partdef>[,<partdef>]
46 <mtd-id> := unique id used in mapping driver/device
47 <size> := standard linux memsize OR "-" to denote all
57 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
58 mtdparts=sa1100:-
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/nvmem/layouts/
Du-boot,env.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/nvmem/layouts/u-boot,env.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: U-Boot environment variables layout
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).
27 - Rafał Miłecki <[email protected]>
32 - description: A standalone env data block
[all …]
/linux-6.14.4/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 <[email protected]>
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 <[email protected]>
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 …]
/linux-6.14.4/Documentation/devicetree/bindings/mtd/partitions/
Dbinman.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/binman.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 partition. There are quite a number of binman-specific entry types, such as
18 - Simon Glass <[email protected]>
21 - $ref: /schemas/mtd/partitions/partition.yaml#
26 - u-boot # u-boot.bin from U-Boot project
27 - tfa-bl31 # bl31.bin or bl31.elf from TF-A project
30 - compatible
[all …]
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 bootloader commonly used in embedded devices. It's almost always
17 - Rafał Miłecki <[email protected]>
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 <[email protected]>
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 …]
Dpartition.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/partition.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
16 Everything after 'partition-' will be used as the partition name to compare
26 - Rafał Miłecki <[email protected]>
37 read-only:
39 should only be mounted read-only. This is usually used for flash
40 partitions containing early-boot firmware images or data which should
49 slc-mode:
[all …]
Dlinksys,ns-partitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/linksys,ns-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.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
19 - Rafał Miłecki <[email protected]>
25 const: linksys,ns-partitions
27 "#address-cells":
30 "#size-cells":
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/mmc/
Dmmc-card.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mmc/mmc-card.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Ulf Hansson <[email protected]>
13 This documents describes the devicetree bindings for a mmc-host controller
14 child node describing a mmc-card / an eMMC.
17 partition, the 2 BOOT partition (boot1/2) and the 4 GP (gp1/2/3/4) if supported
22 const: mmc-card
27 broken-hpi:
[all …]
/linux-6.14.4/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 …]
/linux-6.14.4/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 {
/linux-6.14.4/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 …]
/linux-6.14.4/arch/arm/boot/dts/marvell/
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 …]
Darmada-385-db-88f6820-amc.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
4 * (DB-88F6820-AMC)
9 /dts-v1/;
10 #include "armada-385.dtsi"
12 #include <dt-bindings/gpio/gpio.h>
16 compatible = "marvell,a385-db-amc", "marvell,armada385", "marvell,armada380";
19 stdout-path = "serial0:115200n8";
40 pinctrl-names = "default";
41 pinctrl-0 = <&i2c0_pins>;
51 pinctrl-names = "default";
[all …]
/linux-6.14.4/arch/arm64/boot/dts/marvell/
Darmada-7040-db.dts1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
8 #include <dt-bindings/gpio/gpio.h>
9 #include "armada-7040.dtsi"
13 compatible = "marvell,armada7040-db", "marvell,armada7040",
14 "marvell,armada-ap806-quad", "marvell,armada-ap806";
17 stdout-path = "serial0:115200n8";
31 cp0_exp_usb3_0_current_regulator: gpio-regulator {
32 compatible = "regulator-gpio";
33 regulator-name = "cp0-usb3-0-current-regulator";
34 regulator-type = "current";
[all …]
Darmada-8040-db.dts1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
8 #include <dt-bindings/gpio/gpio.h>
9 #include "armada-8040.dtsi"
13 compatible = "marvell,armada8040-db", "marvell,armada8040",
14 "marvell,armada-ap806-quad", "marvell,armada-ap806";
17 stdout-path = "serial0:115200n8";
34 cp0_reg_usb3_0_vbus: cp0-usb3-0-vbus {
35 compatible = "regulator-fixed";
36 regulator-name = "cp0-usb3h0-vbus";
37 regulator-min-microvolt = <5000000>;
[all …]
/linux-6.14.4/arch/arm/boot/dts/qcom/
Dqcom-ipq4018-jalapeno.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
4 #include "qcom-ipq4019.dtsi"
5 #include <dt-bindings/gpio/gpio.h>
6 #include <dt-bindings/input/input.h>
14 mdio_pins: mdio-state {
15 mdio-pins {
18 bias-pull-up;
21 mdc-pins {
24 bias-pull-up;
28 serial_pins: serial-state {
[all …]

12345678910>>...14