| /rk3399_rockchip-uboot/doc/device-tree-bindings/ |
| H A D | README | 6 These follow along with Linux kernel bindings, with a few additions. By
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/video/ |
| H A D | display-timing.txt | 39 All the optional properties that are not bool follow the following logic:
|
| /rk3399_rockchip-uboot/board/rockchip/gva_rk3229/ |
| H A D | README | 59 please follow google's documents.)
|
| /rk3399_rockchip-uboot/fs/yaffs2/ |
| H A D | yaffsfs.c | 1795 const void *data, int size, int flags, int follow) in yaffs_do_setxattr() argument
1818 if (follow) in yaffs_do_setxattr()
1884 void *data, int size, int follow) in yaffs_do_getxattr() argument
1906 if (follow) in yaffs_do_getxattr()
1968 int size, int follow) in yaffs_do_listxattr() argument
1990 if (follow) in yaffs_do_listxattr()
2053 int follow) in yaffs_do_removexattr() argument
2075 if (follow) in yaffs_do_removexattr()
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/pinctrl/ |
| H A D | st,stm32-pinctrl.txt | 60 pin-functions nodes follow...
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.dfutftp | 99 To create FIT image for download one should follow the update tftp README file
|
| H A D | README.mxsimage | 49 - After a "TAG" unstruction, any of the following instructions may follow
|
| H A D | README.drivers.eth | 215 should logically follow.
|
| H A D | README.trace | 34 this, follow these steps:
|
| H A D | README.odroid | 99 delivered with the board on the eMMC/SD card. Then follow the steps:
|
| H A D | README.efi | 126 Here follow a few implementation notes for those who want to fiddle with
|
| H A D | README.distro | 266 For suggestions on memory locations for ARM systems, you must follow the
|
| H A D | README.x86 | 815 information (eg: E820) from. The table unfortunately has to follow the coreboot
911 easy to fit it in. You can follow the Minnowboard Max implementation, for
|
| /rk3399_rockchip-uboot/doc/uImage.FIT/ |
| H A D | x86-fit-boot.txt | 251 follow
|
| /rk3399_rockchip-uboot/doc/driver-model/ |
| H A D | of-plat.txt | 50 - Naming of nodes and properties is automatic. This means that they follow
|
| /rk3399_rockchip-uboot/arch/arm/dts/ |
| H A D | rk3288-veyron.dtsi | 382 * make it easier to follow the schematic. The signals
|
| /rk3399_rockchip-uboot/test/py/ |
| H A D | README.md | 324 follow:
|
| /rk3399_rockchip-uboot/Licenses/ |
| H A D | gpl-2.0.txt | 57 modification follow.
|
| H A D | lgpl-2.1.txt | 110 modification follow. Pay close attention to the difference between a
|
| H A D | lgpl-2.0.txt | 94 modification follow. Pay close attention to the difference between a
|
| /rk3399_rockchip-uboot/tools/binman/ |
| H A D | README | 232 immediately follow the SPL binary.
|
| /rk3399_rockchip-uboot/tools/buildman/ |
| H A D | README | 1000 By default buildman considers the follow two configuration methods
|
| /rk3399_rockchip-uboot/ |
| H A D | README | 223 SPL and U-Boot proper (i.e. they both follow the same rules).
3750 to port U-Boot to your hardware platform. To do this, follow these
4674 Immediately after the terminating 0 follow the images, one by
|