| /rk3399_rockchip-uboot/doc/ |
| H A D | README.console | 40 putc (to put a char to stdout) 41 puts (to put a string to stdout) 42 printf (to format and put a string to stdout) 49 eputc (to put a char to stderr) 50 eputs (to put a string to stderr) 51 eprintf (to format and put a string to stderr)
|
| H A D | README.fdt-control | 110 to set the filename of the device tree source. Then put your device tree 148 Then U-Boot will copy that file to u-boot.dtb, put it in the .img file 151 If you wish to put the fdt at a different address in memory, you can 162 To use this, put something like this in your board header file:
|
| H A D | README.pblimage | 68 character to put comments
|
| H A D | README.kwbimage | 47 character to put comments
|
| H A D | README.imximage | 47 character to put comments. 195 to not overwrite the space where I will put u-boot.
|
| H A D | README.nvme | 31 do necessary initialization to put the controller into a ready state at which
|
| H A D | README.dfutftp | 86 3. If required, to update firmware on boot, put the "dfu tftp 0 mmc 0" in the
|
| H A D | README.ublimage | 39 character to put comments.
|
| H A D | README.x86 | 112 Make sure all these binary blobs are put in the board directory. 218 Rename the first one to fsp.bin and second one to cmc.bin and put them in the 243 website and put the .fd file (CHIEFRIVER_FSP_GOLD_001_09-OCTOBER-2013.fd at the 268 Obtain the VGA RAM (Vga.dat at the time of writing) and put it into the same 345 Rename the file and put it to the board directory by: 718 U-Boot prints out some bootstage timing. This is more useful if you put the 782 If you want to put this in a script you can use something like this: 1088 put the board to S3 state where the power is off. So when the power button is
|
| H A D | README.power-framework | 164 profile it should be put to a separate file.
|
| /rk3399_rockchip-uboot/board/freescale/common/ |
| H A D | Kconfig | 20 esbc_halt - put the core in spin loop (Secure Boot Only)
|
| /rk3399_rockchip-uboot/arch/x86/cpu/queensbay/ |
| H A D | Kconfig | 34 specific code which must be put in the flash for the processor to 51 put in flash at a location matching the strap-determined base address.
|
| /rk3399_rockchip-uboot/board/warp7/ |
| H A D | README | 24 Remove the CPU board from the base board then put switch 2 in the upper 61 Put warp7 board into normal boot mode (put the switch 2 in the lower position)
|
| /rk3399_rockchip-uboot/lib/zlib/ |
| H A D | inflate.c | 180 put = strm->next_out; \ 191 strm->next_out = put; \ 332 unsigned char FAR *put; /* next output */ in inflate() local 599 zmemcpy(put, next, copy); in inflate() 603 put += copy; in inflate() 834 from = put - state->offset; in inflate() 841 *put++ = *from++; in inflate() 847 *put++ = (unsigned char)(state->length); in inflate() 859 UPDATE(state->check, put - out, out); in inflate()
|
| /rk3399_rockchip-uboot/arch/x86/cpu/quark/ |
| H A D | Kconfig | 32 machine-specific code which must be put in the flash for the RMU 50 put in flash at a location matching the strap-determined base address.
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/clock/ |
| H A D | rockchip.txt | 13 structure a matter of taste, as either all gates can be put into
|
| /rk3399_rockchip-uboot/tools/patman/ |
| H A D | README | 24 each time. So for example if you put: 85 used. Failing that you can put it into your path or ~/bin/checkpatch.pl 188 patman does not yet use it, but it is convenient to put the branch 210 together and put after the cover letter. Can appear multiple 223 probably a bug). If you put this tag in your patches, it will 451 2. If you put tags in the subject, patman will Cc the maintainers
|
| /rk3399_rockchip-uboot/tools/buildman/ |
| H A D | builderthread.py | 459 self.builder.out_queue.put(result) 467 self.builder.out_queue.put(result)
|
| /rk3399_rockchip-uboot/board/bosch/shc/ |
| H A D | README | 42 -> now you have the MLO and the u-boot.img file, you can put
|
| /rk3399_rockchip-uboot/tools/binman/ |
| H A D | README | 110 Where possible it is best to put as much as possible in the FIT, with binman 236 the entry (blob, u-boot) tells binman what to put there. For 'blob' we must 244 name. If you want to put the same binary in the image multiple times, you can 292 put into the entry. If binman knows about the entry type (like 340 image, put this property in the binman node. For example, this will 431 a common header. You can then put the binman node (and anything else that is
|
| /rk3399_rockchip-uboot/tools/ |
| H A D | genboardscfg.py | 219 queue.put(kconf_scanner.scan(defconfig))
|
| /rk3399_rockchip-uboot/drivers/mtd/ubi/ |
| H A D | Kconfig | 56 To put it differently, if this value is 20, UBI will try to reserve
|
| /rk3399_rockchip-uboot/doc/SPL/ |
| H A D | README.am335x-network | 74 Install TFTP server and put image files to it's root directory
|
| /rk3399_rockchip-uboot/board/freescale/mpc8349itx/ |
| H A D | README | 140 Therefore, just put a U-Boot image at both FE000000 and FEF00000 and
|
| /rk3399_rockchip-uboot/doc/uImage.FIT/ |
| H A D | beaglebone_vboot.txt | 25 simply generate a new key and put his public key into U-Boot so that 198 At the same time we must put the public key into U-Boot device tree, with the 411 (/images/kernel@1). We could just put a new kernel in the image, but we will
|