Home
last modified time | relevance | path

Searched refs:partitions (Results 1 – 25 of 54) sorted by relevance

123

/rk3399_rockchip-uboot/doc/
H A DREADME.gpt16 - partitions - lists of available partitions (defined at u-boot):
27 GPT for marking disks/partitions is using the UUID. It is supposed to be a
102 40 8 B First usable LBA for partitions (primary partition table last
153 Creating GPT partitions in U-Boot:
158 Format of partitions layout:
187 gpt write mmc 0 $partitions
189 Checking (validating) GPT partitions in U-Boot:
195 gpt verify mmc 0 [$partitions]
197 where [$partitions] is an optional parameter.
202 offset (last two in LBA) - are compared with data defined in '$partitions'
[all …]
H A DREADME.JFFS2_NAND7 Configuration of partitions is similar to how this is done in U-Boot
H A DREADME.android-fastboot57 aliases when accessing partitions by name (flash_write and erase functions).
65 partitions (currently on eMMC). Target partitions are referred on the host
70 For MBR the partitions are referred by generic names according to the
H A DREADME.imximage138 You should start clearing the partitions table on the SD card. Because
193 you can set additional partitions to store rootfs, data, etc.
/rk3399_rockchip-uboot/disk/
H A Dpart_efi.c652 disk_partition_t *partitions, int parts) in gpt_fill_pte() argument
677 lbaint_t start = partitions[i].start; in gpt_fill_pte()
678 lbaint_t size = partitions[i].size; in gpt_fill_pte()
711 str_type_guid = partitions[i].type_guid; in gpt_fill_pte()
732 str_uuid = partitions[i].uuid; in gpt_fill_pte()
746 if (partitions[i].bootable) in gpt_fill_pte()
752 dosname_len = sizeof(partitions[i].name); in gpt_fill_pte()
759 (efi_char16_t)(partitions[i].name[k]); in gpt_fill_pte()
763 __func__, partitions[i].name, i, in gpt_fill_pte()
847 disk_partition_t *partitions, int parts_count) in gpt_restore() argument
[all …]
/rk3399_rockchip-uboot/cmd/
H A Dgpt.c376 disk_partition_t **partitions, in set_gpt_info() argument
541 *partitions = parts; in set_gpt_info()
558 disk_partition_t *partitions = NULL; in gpt_default() local
562 &str_disk_guid, &partitions, &part_count); in gpt_default()
574 ret = gpt_restore(blk_dev_desc, str_disk_guid, partitions, part_count); in gpt_default()
576 free(partitions); in gpt_default()
584 disk_partition_t *partitions = NULL; in gpt_verify() local
592 &str_disk_guid, &partitions, &part_count); in gpt_verify()
608 ret = gpt_verify_partitions(blk_dev_desc, partitions, part_count, in gpt_verify()
611 free(partitions); in gpt_verify()
[all …]
/rk3399_rockchip-uboot/board/freescale/mx35pdk/
H A DREADME39 Linux partitions:
45 Creating 5 MTD partitions on "NAND 2GiB 3,3V 8-bit":
52 Creating 6 MTD partitions on "mxc_nor_flash.0":
60 NAND partitions can be recognized enabling in kernel CONFIG_MTD_REDBOOT_PARTS.
88 Creating 6 MTD partitions on "mxc_nor_flash.0":
/rk3399_rockchip-uboot/doc/mvebu/cmd/
H A Dbubt.txt38 - The eMMC has 2 boot partitions (BOOT0 and BOOT1) and a user data partition (DATA).
39 The boot partitions are numbered as partition 1 and 2 in MMC driver.
47 The eMMC has 2 boot partitions (BOOT0 and BOOT1) and a user data partition (DATA).
48 The boot partitions are numbered as partition 1 and 2 in MMC driver.
/rk3399_rockchip-uboot/include/
H A Dpart.h329 disk_partition_t *partitions, int parts);
355 disk_partition_t *partitions, const int parts_count);
409 disk_partition_t *partitions, int parts,
/rk3399_rockchip-uboot/drivers/block/
H A DKconfig10 be partitioned into several areas, called 'partitions' in U-Boot.
22 be partitioned into several areas, called 'partitions' in U-Boot.
/rk3399_rockchip-uboot/drivers/mtd/
H A Dmtdpart.c71 list_for_each_entry(slave, &master->partitions, node) { in mtd_partitions_used()
538 list_for_each_entry_safe(slave, next, &master->partitions, node) { in do_del_mtd_partitions()
669 INIT_LIST_HEAD(&slave->partitions); in allocate_partition()
811 list_for_each_entry(p, &master->partitions, node) { in mtd_add_partition()
821 list_add_tail(&new->node, &master->partitions); in mtd_add_partition()
840 list_for_each_entry_safe(slave, next, &master->partitions, node) in mtd_del_partition()
882 list_add_tail(&slave->node, &master->partitions); in add_mtd_partitions()
/rk3399_rockchip-uboot/doc/device-tree-bindings/mtd/spi/
H A Dspi-flash.txt5 representing partitions.
/rk3399_rockchip-uboot/board/ti/omap5_uevm/
H A DREADME11 boot partitions using (name depending on documentation referenced)
/rk3399_rockchip-uboot/board/ti/dra7xx/
H A DREADME11 boot partitions using (name depending on documentation referenced)
/rk3399_rockchip-uboot/doc/device-tree-bindings/mtd/
H A Dmtd-physmap.txt17 sub-nodes representing partitions (see below). In this case
44 The device tree may optionally contain sub-nodes describing partitions of the
H A Daltera_qspi.txt19 For partitions inside each flash, please refer to /mtd/partition.txt
/rk3399_rockchip-uboot/board/Arcturus/ucp1020/
H A DREADME50 into defined NOR flash partitions. Examples:
/rk3399_rockchip-uboot/arch/arm/dts/
H A Darmada-7040-db.dts130 partitions {
131 compatible = "fixed-partitions";
H A Darmada-8040-mcbin.dts247 partitions {
248 compatible = "fixed-partitions";
H A Darmada-7040-db-nand.dts137 partitions {
138 compatible = "fixed-partitions";
H A Darmada-8040-db.dts259 partitions {
260 compatible = "fixed-partitions";
H A Darmada-385-turris-omnia.dts360 partitions {
361 compatible = "fixed-partitions";
/rk3399_rockchip-uboot/board/davinci/da8xxevm/
H A DREADME.da85078 Alternatively, MTD partitions may be defined. Using "mtdparts" to
98 space at the start of the mmc when creating the partitions)
/rk3399_rockchip-uboot/board/bosch/shc/
H A DREADME114 switch to partitions #0, OK
/rk3399_rockchip-uboot/include/linux/mtd/
H A Dmtd.h336 struct list_head partitions; member
371 return !list_empty(&mtd->partitions); in mtd_has_partitions()

123