Home
last modified time | relevance | path

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

12345678910>>...14

/freebsd/sys/contrib/device-tree/Bindings/mtd/partitions/
H A Dfixed-partitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/fixe
[all...]
H A Dnvmem-cells.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/nvme
[all...]
H A Dlinux,ubi.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/linux,ubi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 physical flash device and spreads the I/O load (i.e wear-leveling)
16 - Daniel Golle <daniel@makrotopia.org>
19 - $ref: partition.yaml#
30 "^ubi-volume-.*$":
31 $ref: /schemas/mtd/partitions/ubi-volume.yaml#
36 - compatible
[all …]
H A Dbrcm,bcm947xx-cfe-partitions.txt1 Broadcom BCM47xx Partitions
5 home routers. Their BCM947xx boards using CFE bootloader have several partitions
6 without any on-flash partition table. On some devices their sizes and/or
7 meanings can also vary so fixed partitioning can't be used.
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
[all …]
H A Dpartitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Partitions
10 This binding is generic and describes the content of the partitions container
14 - Miquel Raynal <miquel.raynal@bootlin.com>
17 - $ref: arm,arm-firmware-suite.yaml
18 - $ref: brcm,bcm4908-partitions.yaml
19 - $ref: brcm,bcm947xx-cfe-partitions.yaml
[all …]
H A Dbrcm,bcm947xx-cfe-partitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm947xx-cfe-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Broadcom BCM47xx Partitions
12 partitions without any on-flash partition table. On some devices their sizes
13 and/or meanings can also vary so fixed partitioning can't be used.
15 Discovering partitions on these devices is possible thanks to having a special
19 Most of partitions use ASCII text based magic for determining a type. More
20 complex partitions (like TRX with its HDR0 magic) may include extra header
[all …]
H A 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 <rafal@milecki.pl>
25 const: linksys,ns-partitions
27 "#address-cells":
30 "#size-cells":
[all …]
H A Dbrcm,bcm4908-partitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm4908-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 Broadcom BCM4908 CFE bootloader supports two firmware partitions. One is used
13 This binding allows defining all fixed partitions and marking those containing
18 - Rafał Miłecki <rafal@milecki.pl>
24 const: brcm,bcm4908-partitions
26 "#address-cells":
29 "#size-cells":
[all …]
H A Dbrcm,bcm963xx-cfe-nor-partitions.txt1 Broadcom BCM963XX CFE Loader NOR Flash Partitions
6 NVRAM partition, and the remainder in-between for one to two firmware partitions
7 at fixed offsets. A valid firmware partition is identified by the ImageTag
12 - compatible : must be "brcm,bcm963xx-cfe-nor-partitions"
17 compatible = "cfi-flash";
19 bank-width = <2>;
21 partitions {
22 compatible = "brcm,bcm963xx-cfe-nor-partitions";
H A 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 <sjg@chromium.org>
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 …]
/freebsd/sys/contrib/device-tree/src/arm64/marvell/
H A 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 …]
H A 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 …]
/freebsd/sys/contrib/device-tree/src/arm/ti/omap/
H A 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";
17 /* Power supply provides a fixed 3.3V @3A */
18 vmmcsd_fixed: vmmcsd-regulator {
19 compatible = "regulator-fixe
[all...]
/freebsd/usr.bin/mkimg/
H A Dmkimg.140 .Op Fl -capacity Ar capacity
48 .Fl -formats | Fl -schemes | Fl -version
69 The disk image can be made bootable by specifying the scheme-specific boot
78 utility does not treat it any differently from other partitions.
110 partitions and to round the size of the disk image.
123 option, but without specifying any partitions.
124 When the size required for all the partitions is larger than the
131 If the combined sizes of the given partitions exceed the size given with
136 .Fl -capacity
174 No partitions are marked active when the value is 0.
[all …]
/freebsd/sys/contrib/device-tree/Bindings/mtd/
H A 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 …]
H A Dpartition.txt1 Flash partitions in device tree
7 Different devices may be partitioned in a different ways. Some may use a fixed
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 Deprecated: partitions defined in flash node
30 For backwards compatibility partitions as direct subnodes of the flash device are
[all …]
H A Dqcom_nandc.txt4 - compatible: must be one of the following:
5 * "qcom,ipq806x-nand" - for EBI2 NAND controller being used in IPQ806x
7 * "qcom,ipq4019-nand" - for QPIC NAND controller v1.4.0 being used in
9 * "qcom,ipq6018-nand" - for QPIC NAND controller v1.5.0 being used in
11 * "qcom,ipq8074-nand" - for QPIC NAND controller v1.5.0 being used in
13 * "qcom,sdx55-nand" - for QPIC NAND controller v2.0.0 being used in
16 - reg: MMIO address range
17 - clocks: must contain core clock and always on clock
18 - clock-names: must contain "core" for the core clock and "aon" for the
22 - dmas: DMA specifier, consisting of a phandle to the ADM DMA
[all …]
H A 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 …]
/freebsd/sys/contrib/device-tree/Bindings/nvmem/
H A Du-boot,env.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/nvmem/u-boo
[all...]
/freebsd/sys/contrib/device-tree/src/arm/broadcom/
H A Dbcm53016-meraki-mr32.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
6 * Copyright (C) 2018-2020 Christian Lamparter <chunkeey@gmail.com>
9 /dts-v1/;
12 #include "bcm5301x-nand-cs0-bch8.dtsi"
13 #include <dt-bindings/leds/common.h>
33 compatible = "gpio-leds";
39 panic-indicator;
49 compatible = "gpio-keys";
51 button-restart {
58 pwm-leds {
[all …]
/freebsd/sys/contrib/device-tree/Bindings/nvmem/layouts/
H A 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 <rafal@milecki.pl>
32 - description: A standalone env data block
[all …]
/freebsd/sys/contrib/device-tree/src/arm/marvell/
H A 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 …]
H A 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 …]
/freebsd/sys/contrib/device-tree/src/arm/qcom/
H A 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 …]
/freebsd/contrib/llvm-project/lld/docs/
H A DPartitions.rst1 Partitions title
10 or a shared library) to be split into multiple pieces, or partitions. A
12 loadable partitions. The loadable partitions depend on the main partition
14 shared object, the main partition and the loadable partitions share a virtual
15 address space at link time, and each loadable partition is assigned a fixed
16 offset from the main partition. This allows the loadable partitions to refer
21 -----
37 ``-fsymbol-partition=<soname>``, where ``<soname>`` is the intended soname
42 into partitions according to which sections of the program are reachable from
43 which entry points, similarly to how ``--gc-sections`` removes unused parts of
[all …]

12345678910>>...14