| /rk3399_rockchip-uboot/tools/buildman/ |
| H A D | test.py | 187 build = builder.Builder(self.toolchains, base_dir, None, 1, 2, 189 build.do_make = self.Make 192 build.BuildBoards(self.commits, board_selected, keep_outputs=False, 203 build.SetDisplayOptions(show_errors=True); 204 build.ShowSummary(self.commits, board_selected) 358 def CheckDirs(self, build, dirname): argument 359 self.assertEqual('base%s' % dirname, build._GetOutputDir(1)) 361 build.GetBuildDir(1, 'fred')) 363 build.GetDoneFile(1, 'fred')) 365 build.GetFuncSizesFile(1, 'fred', 'u-boot')) [all …]
|
| H A D | README | 11 If you just want to quickly set up buildman so you can build something (for 26 with your patch series. It can build each individual commit and report 58 directories, which you can look at while the build is progressing, or when 61 Buildman is designed to build entire git branches, i.e. muliple commits. It 64 commit). It is possible to build a branch for one board, then later build it 65 for another board. If you want buildman to re-build a commit it has already 80 incremental build. Eventually the thread reaches the last commit and stops. 82 after every commit, and your build will be very slow. This is because a 84 incremental build. 101 builds the upstream commit as well, for comparison. It cannot build [all …]
|
| /rk3399_rockchip-uboot/board/hisilicon/hikey/ |
| H A D | build-tf.mak | 15 @echo "make -f build-tf.mak build" 29 build: have-crosscompiler FORCE target 31 rm -rf build/ 39 cp build/hikey/debug/bl1.bin $(output_dir)/bl1-hikey.bin 40 cp build/hikey/debug/fip.bin $(output_dir)/fip-hikey.bin
|
| /rk3399_rockchip-uboot/test/ |
| H A D | run | 4 ./test/py/test.py --bd sandbox --build 7 ./test/py/test.py --bd sandbox_spl --build -k test/py/tests/test_ofplatdata.py 10 ./test/py/test.py --bd sandbox_flattree --build
|
| /rk3399_rockchip-uboot/board/bosch/shc/ |
| H A D | Kconfig | 52 activate, if you want to build for the B sample version 58 activate, if you want to build for the B2 sample version 64 activate, if you want to build for the C sample version 70 activate, if you want to build for the C2 sample version 76 activate, if you want to build for the C3 sample version 82 activate, if you want to build for the Series version
|
| /rk3399_rockchip-uboot/arch/arm/lib/ |
| H A D | stacktrace_64.c | 67 char *build = "tpl"; in dump_core_stack() local 69 char *build = "spl"; in dump_core_stack() local 71 char *build = ""; in dump_core_stack() local 102 "./scripts/stacktrace.sh dump.txt %s\n\n", build); in dump_core_stack()
|
| H A D | elf_arm_efi.lds | 63 .note.gnu.build-id : { *(.note.gnu.build-id) }
|
| H A D | elf_aarch64_efi.lds | 63 .note.gnu.build-id : { *(.note.gnu.build-id) }
|
| /rk3399_rockchip-uboot/ |
| H A D | Makefile | 406 $(Q)$(MAKE) $(build)=scripts/basic 483 $(Q)$(MAKE) $(build)=scripts/kconfig $@ 486 $(Q)$(MAKE) $(build)=scripts/kconfig $@ 498 $(Q)$(MAKE) $(build)=$(@) 892 $(Q)$(MAKE) $(build)=dts dtbs 1108 $(Q)$(MAKE) $(build)=arch/arm/mach-imx $@ 1111 $(Q)$(MAKE) $(build)=arch/arm/mach-imx $@ 1129 $(Q)$(MAKE) $(build)=arch/arm/cpu/arm926ejs/mxs u-boot-signed.sb 1131 $(Q)$(MAKE) $(build)=arch/arm/cpu/arm926ejs/mxs u-boot.sb 1314 $(Q)$(MAKE) $(build)=$@ [all …]
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.socfpga | 25 Updated/working projects should build using either process below. 43 build the project: 61 $ /path/to/bsb/tools/bsp-create-settings --type spl --bsp-dir build \ 63 --settings build/settings.bsp 65 You should use the bsp "build" directory above (ie, where the settings.bsp file is) 67 are updated for a given project build, u-boot should be configured for the 68 project board (eg, de0-nano-sockit) and then build the normal spl build.
|
| H A D | README.spear | 36 spear320 build with environment variables placed at default 43 spear320 build with environment variables placed in NAND device 45 spear320 build with usbtty terminal as default and environment 48 spear320 build with usbtty terminal as default and environment
|
| H A D | README.ag101p | 29 build: 31 2. Use `make adp-ag101p_defconfig` in u-boot root to build the image.
|
| H A D | README.mpc85xx-sd-spi-boot | 5 boot_format is a tool to write SD bootable images to a filesystem and build 22 Run the following to build this project 39 For build binary images directly a local file:
|
| H A D | README.pblimage | 18 To build the eSPI boot image: 22 To build the SD boot image: 26 To build the NAND boot image:
|
| H A D | README.fdt-control | 168 After board configuration is done, fdt supported u-boot can be build in two ways: 169 1) build the default dts which is defined from CONFIG_DEFAULT_DEVICE_TREE 171 2) build the user specified dts file 178 U-Boot is designed to build with a single architecture type and CPU 179 type. So for example it is not possible to build a single ARM binary 182 the CPU families within arch/arm/cpu/arm926ejs (omap or at91) at build 183 time. Similarly you cannot build for multiple cpu types or
|
| H A D | README.marvell | 31 5. Configure the device-tree and build the U-Boot image: 47 The ARM Trusted Firmware (ATF) build process uses this image to generate the
|
| /rk3399_rockchip-uboot/arch/arm/mach-bcm283x/ |
| H A D | Kconfig | 44 This option creates a build targetting the ARM1176 ISA. 67 This option creates a build targetting the ARMv7/AArch32 ISA. 71 bool "Raspberry Pi 3 32-bit build" 83 This option creates a build targetting the ARMv7/AArch32 ISA. 87 bool "Raspberry Pi 3 64-bit build" 111 This option creates a build targetting the ARMv8/AArch64 ISA.
|
| /rk3399_rockchip-uboot/board/ti/omap5_uevm/ |
| H A D | README | 4 This document covers various features of the 'omap5_uevm' build and some 13 example we load MLO and u-boot.img from the build into DDR and then use
|
| /rk3399_rockchip-uboot/board/ti/dra7xx/ |
| H A D | README | 4 This document covers various features of the 'dra7xx_evm' build and some 13 example we load MLO and u-boot.img from the build into DDR and then use
|
| /rk3399_rockchip-uboot/board/freescale/mx6sabreauto/ |
| H A D | README | 1 How to use and build U-Boot on mx6sabreauto 6 In order to build it: 29 In order to build it:
|
| /rk3399_rockchip-uboot/board/coreboot/coreboot/ |
| H A D | Kconfig | 33 directory to be used to build U-Boot for coreboot. 40 arch/x86/dts/ directory to be used to build U-Boot for coreboot.
|
| /rk3399_rockchip-uboot/common/spl/ |
| H A D | Kconfig | 17 If you want to build SPL as well as the normal image, say Y. 31 Support to build SPL as decomp header. 302 may improve boot performance. Enable this option to build the 303 drivers in drivers/cpu as part of an SPL build. 310 this option to build the drivers in drivers/crypto as part of an 311 SPL build. 318 this option to build the drivers in drivers/keylad as part of an 319 SPL build. 328 this option to build system-specific drivers for hash acceleration 329 as part of an SPL build. [all …]
|
| /rk3399_rockchip-uboot/common/usbplug/ |
| H A D | Kconfig | 7 Support to build U-Boot as usb plug image for download firmware.
|
| /rk3399_rockchip-uboot/drivers/mtd/ubi/ |
| H A D | Makefile | 8 obj-y += attach.o build.o vtbl.o vmt.o upd.o kapi.o eba.o io.o wl.o crc32.o
|
| /rk3399_rockchip-uboot/cmd/ |
| H A D | version.c | 30 printf("coreboot-%s (%s)\n", lib_sysinfo.version, lib_sysinfo.build); in do_version()
|