| /rk3399_rockchip-uboot/drivers/mtd/ |
| H A D | mtdcore.h | 12 int parse_mtd_partitions(struct mtd_info *master, const char * const *types,
|
| H A D | mtdpart.c | 962 int parse_mtd_partitions(struct mtd_info *master, const char *const *types, in parse_mtd_partitions() argument 969 if (!types) in parse_mtd_partitions() 970 types = default_mtd_part_types; in parse_mtd_partitions() 972 for ( ; ret <= 0 && *types; types++) { in parse_mtd_partitions() 973 parser = get_partition_parser(*types); in parse_mtd_partitions() 974 if (!parser && !request_module("%s", *types)) in parse_mtd_partitions() 975 parser = get_partition_parser(*types); in parse_mtd_partitions()
|
| /rk3399_rockchip-uboot/board/samsung/common/ |
| H A D | Makefile | 15 obj-$(CONFIG_BOARD_TYPES) += exynos5-dt-types.o
|
| /rk3399_rockchip-uboot/drivers/usb/host/ |
| H A D | usb-sandbox.c | 22 static const char types[] = "ZICB"; in usbmon_trace() local 26 debug("0 0 S %c%c:%d:%03ld:%ld", types[type], in usbmon_trace()
|
| /rk3399_rockchip-uboot/board/emulation/ |
| H A D | Kconfig | 17 There are two types of x86 boards supported by QEMU which are
|
| /rk3399_rockchip-uboot/doc/uImage.FIT/ |
| H A D | source_file_format.txt | 161 - type : Name of component sub-image type, supported types are: 170 - os : OS name, mandatory for types "kernel" and "ramdisk". Valid OS names 174 - arch : Architecture name, mandatory for types: "standalone", "kernel", 180 '#address-cells' property of the root node. Mandatory for for types: 183 property of the root node. Mandatory for types: "standalone" and "kernel".
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.mips | 38 * Probe CPU types, I-/D-cache and TLB size etc. automatically
|
| H A D | README.unaligned-memory-access.txt | 27 dealing with types such as u16, u32 and u64. 96 Therefore, for standard structure types you can always rely on the compiler 190 1. Casting variables to types of different lengths
|
| H A D | README.m54418twr | 45 - arch/m68k/include/asm/types.h Data types definition
|
| H A D | README.sdp | 69 files and of arbitrary types, e.g.
|
| H A D | README.xtensa | 81 such as "md" are valid. There are two possible types of invalid
|
| /rk3399_rockchip-uboot/drivers/ata/ |
| H A D | Kconfig | 6 types can use this, such as AHCI/SATA. It does not provide any standard
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/net/ |
| H A D | fsl-tsec-phy.txt | 10 "rgmii-rxid" and "rgmii-txid" as all other connection types are detected
|
| /rk3399_rockchip-uboot/drivers/ |
| H A D | Kconfig | 5 # types of drivers sorted in alphabetical order
|
| /rk3399_rockchip-uboot/board/freescale/m53017evb/ |
| H A D | README | 48 - include/asm-m68k/types.h Data types definition
|
| /rk3399_rockchip-uboot/doc/SPI/ |
| H A D | README.dual-flash | 12 "dual_flash" from include/spi.h describes these types of connection mode
|
| /rk3399_rockchip-uboot/tools/binman/ |
| H A D | README | 129 image types. These can be listed by running 'mkimage -T list'. Examples 291 For 'blob' types this provides the filename containing the binary to 469 data from a file and places it in the entry. In fact most entry types are 474 New entry types can be supported by adding new files in that directory. 505 image. The difficulty comes from the wide variety of input types (simple 515 New entry types should aim to provide simple usage where possible. If new
|
| /rk3399_rockchip-uboot/board/freescale/m52277evb/ |
| H A D | README | 50 - include/asm-m68k/types.h Data types definition
|
| /rk3399_rockchip-uboot/board/freescale/m547xevb/ |
| H A D | README | 55 - include/asm-m68k/types.h Data types definition
|
| /rk3399_rockchip-uboot/arch/arm/mach-mvebu/ |
| H A D | Kconfig | 52 # Armada XP/38x SoC types...
|
| /rk3399_rockchip-uboot/board/armltd/integrator/ |
| H A D | README | 38 The makefile contains targets for Integrator platforms of both types
|
| /rk3399_rockchip-uboot/drivers/usb/ |
| H A D | Kconfig | 41 by the USB uclass. Multiple USB controllers of different types
|
| /rk3399_rockchip-uboot/board/freescale/ls1021aqds/ |
| H A D | README | 81 - Supports one DDR3LP UDIMM, of single-, dual- types.
|
| /rk3399_rockchip-uboot/doc/driver-model/ |
| H A D | pmic-framework.txt | 19 At present it's based on two uclass types:
|
| /rk3399_rockchip-uboot/board/freescale/t104xrdb/ |
| H A D | README | 107 - Supports one DDR3LP UDIMM/RDIMMs, of single-, dual- or quad-rank types. 139 - Supports one DDR3LP UDIMM/RDIMMs, of single-, dual- or quad-rank types.
|