Searched refs:creating (Results 1 – 19 of 19) sorted by relevance
| /rk3399_rockchip-uboot/doc/device-tree-bindings/net/ |
| H A D | fixed-link.txt | 8 Such a fixed link situation is described by creating a 'fixed-link'
|
| /rk3399_rockchip-uboot/fs/fat/ |
| H A D | Kconfig | 13 This provides support for creating and writing new files to an
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.lynxkdi | 46 When creating a LynxOS or BlueCat u-boot image using mkimage,
|
| H A D | README.commands | 2 Commands are added to U-Boot by creating a new command structure.
|
| H A D | README.android-fastboot | 123 |creating boot image...
124 |creating boot image - 1847296 bytes
|
| H A D | README.menu | 7 U-Boot provides a set of interfaces for creating and using simple, text
|
| H A D | README.bootmenu | 10 a simple mechanism for creating menus with different boot items.
|
| H A D | README.ti-secure | 44 package for creating a bootable SPL image for secure TI devices.
195 TI SECDEV package for creating a u-boot.img image for secure TI
|
| H A D | README.gpt | 233 creating a disk image as described under 'Block Device Emulation' in
|
| H A D | README.armada-secureboot | 235 employ a dynamic approach of creating a Autoconf-like kwbimage.cfg.in, then
|
| H A D | README.distro | 61 conceptually identical to creating a grub2 configuration file on a desktop
|
| /rk3399_rockchip-uboot/board/sunxi/ |
| H A D | README.nand | 15 creating our images. However, the BROM will use a quite weird pattern
|
| /rk3399_rockchip-uboot/tools/env/ |
| H A D | fw_env.c | 352 int deleting, creating, overwriting; in fw_env_write() local
371 creating = (!oldval && (value && strlen(value))); in fw_env_write()
401 } else if (creating) { in fw_env_write()
|
| /rk3399_rockchip-uboot/board/davinci/da8xxevm/ |
| H A D | README.da850 | 98 space at the start of the mmc when creating the partitions)
|
| /rk3399_rockchip-uboot/doc/driver-model/ |
| H A D | of-plat.txt | 23 bypasses the use of device tree completely, effectively creating a parallel
|
| /rk3399_rockchip-uboot/tools/binman/ |
| H A D | README | 14 So far U-Boot has not provided a way to handle creating such images in a
73 - Each binary can have its own build system and tool chain without creating
|
| /rk3399_rockchip-uboot/arch/x86/ |
| H A D | Kconfig | 249 The build system will take care of creating a u-boot.rom file
|
| /rk3399_rockchip-uboot/tools/buildman/ |
| H A D | README | 522 creating a working directory for each thread, and creating output
|
| /rk3399_rockchip-uboot/ |
| H A D | README | 186 Previously, all configuration was done by hand, which involved creating
788 and in fact, U-Boot does this for you, creating a file called
|