| /u-boot/tools/binman/etype/ |
| A D | fmap.py | 43 def _AddEntries(areas, entry): argument
49 _AddEntries(areas, subentry)
54 areas.append(fmap_util.FmapArea(pos or 0, entry.size or 0,
58 areas = []
60 _AddEntries(areas, entry)
62 areas)
|
| /u-boot/tools/binman/ |
| A D | fmap_util.py | 89 areas = []
94 areas.append(FmapArea(*fields))
96 return header, areas
98 def EncodeFmap(image_size, name, areas): argument
114 values = FmapHeader(FMAP_SIGNATURE, 1, 0, 0, image_size, name, len(areas))
116 for area in areas:
|
| A D | README.entries | 430 provides flashrom with a list of areas, so it knows what it in the flash.
|
| A D | README | 170 these blobs are not relocatable and must be placed at fixed areas in the
|
| /u-boot/board/toradex/colibri_imx7/ |
| A D | colibri_imx7.c | 275 int areas = 1; in ft_board_setup() local
289 areas = 2; in ft_board_setup()
292 ret = fdt_set_usable_memory(blob, start, size, areas); in ft_board_setup()
|
| /u-boot/doc/device-tree-bindings/mtd/ |
| A D | stm32-fmc2-nand.txt | 7 - reg: NAND flash controller memory areas.
11 Regions 5 to 7 contain the same areas for CS1.
|
| /u-boot/drivers/block/ |
| A D | Kconfig | 10 be partitioned into several areas, called 'partitions' in U-Boot.
27 be partitioned into several areas, called 'partitions' in U-Boot.
39 be partitioned into several areas, called 'partitions' in U-Boot.
|
| /u-boot/doc/SPL/ |
| A D | README.omap3 | 49 For the areas that reside within DDR1 they must not be used prior to s_init()
50 completing. Note that CONFIG_SYS_TEXT_BASE must be clear of the areas that SPL
|
| /u-boot/doc/mvebu/ |
| A D | armada-8k-memory.txt | 9 All "Reserved" areas below, are kept for future usage.
|
| /u-boot/doc/ |
| A D | README.memory-test | 38 will happily "test" all such areas, which of course will cause
44 areas used by U-Boot itself - on most systems these are the areas
|
| A D | README.bloblist | 51 different memory areas due to fragmented memory, but it is simpler to just have
|
| A D | README.ubispl | 56 other areas like the kernel/dts load address.
|
| A D | README.nand | 339 unlock consecutive area (can be called multiple times for different areas)
|
| A D | README.POST | 634 following areas will be verified: 0x00000000-0x00000800,
|
| /u-boot/api/ |
| A D | README | 16 functional areas like networking or storage operations
|
| /u-boot/arch/arm/mach-stm32mp/ |
| A D | Kconfig | 106 The areas marked "no-map" in device tree should be located
|
| /u-boot/common/ |
| A D | fdt_support.c | 468 int fdt_set_usable_memory(void *blob, u64 start[], u64 size[], int areas) in fdt_set_usable_memory() argument
474 if (areas > 8) { in fdt_set_usable_memory()
476 __func__, areas, 8); in fdt_set_usable_memory()
491 len = fdt_pack_reg(blob, tmp, start, size, areas); in fdt_set_usable_memory()
|
| /u-boot/doc/device-tree-bindings/pci/ |
| A D | mediatek-pcie.txt | 8 - reg-names: Names of the above areas to use during resource lookup.
|
| /u-boot/doc/imx/habv4/guides/ |
| A D | mx6_mx7_spl_secure_boot.txt | 100 boot. These commands instruct the HAB code on which memory areas of the image
|
| A D | mx6_mx7_secure_boot.txt | 75 boot. These commands instruct the HAB on which memory areas of the image
|
| /u-boot/board/ti/am335x/ |
| A D | README | 40 the IP blocks, so both areas will need their choices updated to reflect
|
| /u-boot/doc/develop/ |
| A D | trace.rst | 343 Tracing could be a little tidier in some areas, for example providing
|
| /u-boot/ |
| A D | MAINTAINERS | 50 Maintainers List (try to look for most precise areas first)
|