| /openbmc/linux/Documentation/driver-api/mmc/ |
| H A D | mmc-dev-parts.rst | 2 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 …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.gpt | 1 # SPDX-License-Identifier: GPL-2.0+
9 - UUID -(Universally Unique Identifier)
10 - GUID - (Globally Unique ID)
11 - EFI - (Extensible Firmware Interface)
12 - UEFI - (Unified EFI) - EFI evolution
13 - GPT (GUID Partition Table) - it is the EFI standard part
14 - partitions - lists of available partitions (defined at u-boot):
20 the gpt command in u-boot.
25 GPT for marking disks/partitions is using the UUID. It is supposed to be a
26 globally unique value. A UUID is a 16-byte (128-bit) number. The number of
[all …]
|
| H A D | README.android-fastboot | 9 ``README.android-fastboot-protocol`` file in the same directory.
13 - ``boot``
14 - ``continue``
15 - ``download``
16 - ``erase`` (if enabled)
17 - ``flash`` (if enabled)
18 - ``getvar``
19 - ``reboot``
20 - ``reboot-bootloader``
21 - ``set_active`` (only a stub implementation which always succeeds)
[all …]
|
| H A D | README.avb2 | 1 Android Verified Boot 2.0
4 Boot 2.0 in U-boot
7 ---------------------------------
8 Verified Boot establishes a chain of trust from the bootloader to system images
10 - Android Boot image: Linux kernel + ramdisk. RAW hashing of the whole
13 - system/vendor partitions: verifying root hash of dm-verity hashtrees.
16 Integrity of the bootloader (U-boot BLOB and environment) is out of scope.
21 1.1. AVB using OP-TEE (optional)
22 ---------------------------------
23 If AVB is configured to use OP-TEE (see 4. below) rollback indexes and
[all …]
|
| H A D | README.mediatek | 1 # SPDX-License-Identifier: GPL-2.0+
7 This document describes how to compile the U-Boot and how to change U-Boot
13 -Set the cross compiler:
15 # export CROSS_COMPILE=/path/to/toolchain/arm-linux-gnueabi-
17 -Clean-up old residuals:
21 -Configure the U-Boot:
26 - For the MT7623n bananapi R2 board use "mt7623n_bpir2_defconfig"
27 - For the MT7629 reference board use "mt7629_rfb_defconfig"
30 Boot sequence
32 -Bootrom -> MTK preloader -> U-Boot
[all …]
|
| /openbmc/u-boot/disk/ |
| H A D | Kconfig | 4 config PARTITIONS config
14 - CONFIG_MAC_PARTITION Apple's MacOS partition table.
15 - CONFIG_DOS_PARTITION MS Dos partition table, traditional on the
17 - CONFIG_ISO_PARTITION ISO partition table, used on CDROM etc.
18 - CONFIG_EFI_PARTITION GPT partition table, common when EFI is the
21 - CONFIG_MTD_PARTITIONS Memory Technology Device partition table.
23 you must configure support for at least one non-MTD partition type
28 depends on PARTITIONS
30 Say Y here if you would like to use device under U-Boot which
35 depends on SPL && PARTITIONS
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mtd/ |
| H A D | qcom,nandc.yaml | 1 # 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 D | ingenic,nand.yaml | 1 # 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 …]
|
| /openbmc/linux/drivers/mtd/parsers/ |
| H A D | Kconfig | 1 # 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 …]
|
| /openbmc/linux/Documentation/devicetree/bindings/nvmem/ |
| H A D | u-boot,env.yaml | 1 # 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 …]
|
| /openbmc/u-boot/board/freescale/mx35pdk/ |
| H A D | README | 2 --------------
6 - CPU module, with CPU, RAM, flash
7 - Personality board, with most interfaces (USB, Network,..)
8 - Debug board with JTAG header.
10 The board is usually delivered with redboot. This howto explains how to boot
11 a linux kernel and how to replace the original bootloader with U-Boot.
14 switch the boot device with the switches SW1-SW2 on the Personality board,
15 and with SW5-SW10 on the Debug board.
18 ---------------------------------------------------
23 exec -c "noinitrd console=ttymxc0,115200 root=/dev/mtdblock8 rw rootfstype=jffs2 ip=dhcp fec_mac=00…
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mtd/partitions/ |
| H A D | u-boot.yaml | 1 # 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 …]
|
| H A D | fixed-partitions.yaml | 1 # 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 …]
|
| H A D | tplink,safeloader-partitions.yaml | 1 # 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 …]
|
| /openbmc/openbmc/poky/scripts/lib/wic/plugins/source/ |
| H A D | bootimg-biosplusefi.py | 13 # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
16 # This implements the 'bootimg-biosplusefi' source plugin class for 'wic'
28 Create MBR + EFI boot partition
30 This plugin creates a boot partition that contains both
31 legacy BIOS and EFI content. It will be able to boot from both.
35 Note it is possible to create an image that can boot from both
36 legacy BIOS and EFI by defining two partitions : one with arg
37 --source bootimg-efi and another one with --source bootimg-pcbios.
39 partitions to be created on the storage device.
40 Both partitions will also be marked as "bootable" which does not work on
[all …]
|
| /openbmc/docs/architecture/code-update/ |
| H A D | emmc-storage-design.md | 7 Created: 2019-06-20
12 filesystem type, partitioning, volume management, boot options and
22 - Security: Ability to enforce read-only, verification of official/signed images
25 - Updatable: Ensure that the filesystem design allows for an effective and
28 - Simplicity: Make the system easy to understand, so that it is easy to develop,
31 - Code reuse: Try to use something that already exists instead of re-inventing
36 - The eMMC image layout and characteristics are specified in a meta layer. This
41 - Code update: Support two versions on flash. This allows a known good image to
44 - GPT partitioning for the eMMC User Data Area: This is chosen over dynamic
48 - Initramfs: An initramfs is needed to run sgdisk on first boot to move the
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0004-FF-A-v15-arm_ffa-introduce-Arm-FF-A-support.patch | 4 Subject: [PATCH] FF-A v15: arm_ffa: introduce Arm FF-A support
6 Add Arm FF-A support implementing Arm Firmware Framework for Armv8-A v1.0
8 The Firmware Framework for Arm A-profile processors (FF-A v1.0) [1]
13 This driver uses 64-bit registers as per SMCCCv1.2 spec and comes
14 on top of the SMCCC layer. The driver provides the FF-A ABIs needed for
15 querying the FF-A framework from the secure world.
18 32-bit data of the Xn registers.
20 All supported ABIs come with their 32-bit version except FFA_RXTX_MAP
21 which has 64-bit version supported.
23 Both 32-bit and 64-bit direct messaging are supported which allows both
[all …]
|
| /openbmc/u-boot/drivers/block/ |
| H A D | Kconfig | 7 flash sticks. These provide a block-level interface which permits
10 be partitioned into several areas, called 'partitions' in U-Boot.
24 flash sticks. These provide a block-level interface which permits
27 be partitioned into several areas, called 'partitions' in U-Boot.
36 flash sticks. These provide a block-level interface which permits
39 be partitioned into several areas, called 'partitions' in U-Boot.
47 This option enables a disk-block cache for all block devices.
48 This is most useful when accessing filesystems under U-Boot since
57 This option enables the disk-block cache in SPL
65 from U-Boot. See also CMD_IDE which provides an 'ide' command for
|
| /openbmc/linux/include/linux/platform_data/ |
| H A D | mtd-nand-s3c2410.h | 1 /* 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 …]
|
| /openbmc/openbmc/poky/scripts/lib/wic/plugins/imager/ |
| H A D | direct.py | 4 # SPDX-License-Identifier: GPL-2.0-only
64 self.name = "%s-%s" % (os.path.splitext(os.path.basename(wks_file))[0],
69 self.parts = self.ks.partitions
71 # as a convenience, set source to the boot partition source
72 # instead of forcing it to be set via bootloader --source
74 if not self.ks.bootloader.source and part.mountpoint == "/boot":
127 device_name = "UUID=%s-%s" % \
136 # mmc device partitions are named mmcblk0p1, mmcblk0p2..
158 return os.path.join(path, "%s-%s.%s" % (self.name, name, extention))
165 For 'wic', we already have our build artifacts - we just create
[all …]
|
| /openbmc/openbmc/poky/scripts/lib/wic/ |
| H A D | help.py | 3 # SPDX-License-Identifier: GPL-2.0-only
35 pager.communicate(hlp.encode('utf-8'))
67 Dispatch to subcommand handler borrowed from combo-layer.
94 usage: wic [--version] | [--help] | [COMMAND [ARGS]]
102 overview wic overview - General overview of wic
103 plugins wic plugins - Overview and API
104 kickstart wic kickstart - wic kickstart reference
118 usage: wic create <wks file or image name> [-o <DIRNAME> | --outdir <DIRNAME>]
119 [-e | --image-name] [-s, --skip-build-check] [-D, --debug]
120 [-r, --rootfs-dir] [-b, --bootimg-dir]
[all …]
|
| /openbmc/u-boot/lib/libavb/ |
| H A D | avb_slot_verify.h | 1 /* SPDX-License-Identifier: MIT */
77 * to boot valid but unverified slots when the device is unlocked.
95 /* AvbPartitionData contains data loaded from partitions when using
103 * Note that this is strictly less than the partition size - it's only
134 /* AvbSlotVerifyData contains data needed to boot a particular slot
135 * and is returned by avb_slot_verify() if partitions in a slot are
138 * All data pointed to by this struct - including data in each item in
139 * the |partitions| array - will be freed when the
144 * value includes the leading underscore - typical values are "" (if
150 * number of elements in this array. The first element -
[all …]
|
| /openbmc/linux/arch/arm/boot/dts/aspeed/ |
| H A D | openbmc-flash-layout.dtsi | 1 // 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";
|
| H A D | openbmc-flash-layout-128.dtsi | 1 // 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";
|
| H A D | openbmc-flash-layout-64.dtsi | 1 // 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";
|