| /rk3399_rockchip-uboot/doc/ |
| H A D | README.OFT | 16 There is a static part which is compiled in with DTC and a dynamic 17 part which is programmatically appended. 19 You'll need a fairly recent DTC tool, which is available by git at 23 The xxd binary dumper is needed too which I got from
|
| H A D | README.omap-ulpi-viewport | 7 register which offers the ulpi phy access so 24 ehci is used in phy mode, which will call ulpi phy reset 26 implementation which will do ulpi reset using the
|
| H A D | README.ubispl | 16 The maximum number of logical eraseblocks which a static volume 30 The maximum volume ids which can be loaded. Used for sizing the 55 which is usually not a problem to reserve in the RAM along with the 88 * in the FLASH which are reserved for the SPL. Think about 121 * we need to subtract the number of blocks which are reserved 134 UBI, so the only non UBI managed FLASH area is the one which is
|
| H A D | README.fsl-hwconfig | 9 This option specifies which of the two oscillator frequencies should be 28 - which controller mode to use 29 - which USB PHY to use
|
| H A D | README.TPL | 22 There has been a directory $(srctree)/spl which contains only a Makefile. The 26 directory spl/tpl. The final binaries which are generated are 33 determine which SPL options to choose based on whether CONFIG_TPL_BUILD
|
| H A D | README.boston | 8 one of which is connected to an Intel EG20T Platform Controller Hub which 28 Please note that QEMU will default to emulating the I6400 CPU which implements
|
| H A D | README.mpc74xx | 11 the BATs. Currently, there are still problems with the code which 13 anyway). Additionally, there is support for enabling the MMU, which
|
| /rk3399_rockchip-uboot/drivers/sysreset/ |
| H A D | Kconfig | 11 Enable system reset drivers which can be used to reset the CPU or 12 board. Each driver can provide a reset method which will be called 20 Enable system reset drivers which can be used to reset the CPU or 21 board. Each driver can provide a reset method which will be called 29 Enable system reset drivers which can be used to reset the CPU or 30 board. Each driver can provide a reset method which will be called
|
| /rk3399_rockchip-uboot/doc/DocBook/ |
| H A D | Makefile | 96 ifeq ($(shell which db2ps >/dev/null 2>&1 && echo found),found) 103 ifeq ($(shell which xmlto >/dev/null 2>&1 && echo found),found) 136 @(which xmlto > /dev/null 2>&1) || \ 147 @(which xmlto > /dev/null 2>&1) || \ 160 @(which fig2dev > /dev/null 2>&1) || \ 169 @(which fig2dev > /dev/null 2>&1) || \
|
| /rk3399_rockchip-uboot/drivers/block/ |
| H A D | Kconfig | 7 flash sticks. These provide a block-level interface which permits 9 devices often have a partition table which allows the device to 19 flash sticks. These provide a block-level interface which permits 21 devices often have a partition table which allows the device to 48 from U-Boot. See also CMD_IDE which provides an 'ide' command for
|
| /rk3399_rockchip-uboot/drivers/video/rk_eink/ |
| H A D | Kconfig | 11 Choose this option to enable support for TPS65185, which is 18 Choose this option to enable support for eink display, which is 20 load kernel logo to ram, which can pass to kernel to display.
|
| /rk3399_rockchip-uboot/doc/SPI/ |
| H A D | README.ti_qspi_flash | 7 has a memory mapped interface which provide direct interface 39 - Newly created file which is responsible for configuring the 40 qspi controller and also for providing the low level api which 46 A seperated file named README.dra_qspi_test has been created which gives all the
|
| /rk3399_rockchip-uboot/doc/driver-model/ |
| H A D | fdt-fixup.txt | 29 system, depending on which daughter boards are connected to the motherboard. 32 device tree overlay mechanism: There exists one "base" device tree, which 39 provide a way to find out if and which daughter boards are installed for this 44 passed to Linux. But since U-Boot's driver model, which is device tree-based as 56 call-back function, which is passed a writeable pointer to the device tree. 60 we have the pre-relocation driver model at our disposal at this stage, which 68 boards have to implement the function board_fix_fdt, which has the following 73 The passed-in void pointer is a writeable pointer to the device tree, which can 119 board_fix_fdt function, in which six GPIO expanders (which might be present or
|
| H A D | usb-info.txt | 94 as a work-around for controllers which can act as USB devices in OTG 117 root hub attached to it. This hub, which is itself a USB device, can provide 118 one or more 'ports' to which additional devices can be attached. It is 119 possible to power up a hub and find out which of its ports have devices 138 (1.5Mbps), full (12Mbps), high (480Mbps) which is only available with USB2 139 and newer (EHCI), and super (5Gbps) which is only available with USB3 and 151 U-Boot simply finds the controller to which the device is attached, and sends 153 properly. Having said that, the USB device which should receive the message 163 These methods use a 'pipe' which is a collection of bit fields used to 171 USB devices are found using a simple algorithm which works through the [all …]
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/exynos/ |
| H A D | isp-spi.txt | 6 which will have a value beyond the maximum number of interrupts exynos5 can 12 - interrupts : A value which is beyond the maximum number of interrupts
|
| H A D | tmu.txt | 10 - samsung,start-warning : Temperature at which TMU starts giving warning (degree celsius) 11 - samsung,start-tripping : Temperature at which TMU shuts down the system (degree celsius) 12 - samsung,hw-tripping : Temperature at which hardware tripping should happen
|
| /rk3399_rockchip-uboot/disk/ |
| H A D | Kconfig | 30 Say Y here if you would like to use device under U-Boot which 66 Say Y here if you would like to use device under U-Boot which 80 Say Y here if you would like to use device under U-Boot which 96 If unsure, leave at 128 entries, which is the standard 109 If unsure, leave at 0 (which will locate the partition 156 Say Y here if you would like to use device under U-Boot which 164 Say Y here if you would like to use device under U-Boot which
|
| /rk3399_rockchip-uboot/drivers/led/ |
| H A D | Kconfig | 7 Many boards have LEDs which can be used to signal status or alerts. 19 All LEDs can blink at the same time but the delay is shared, which 37 This option enables support for this which adds slightly to the 53 Enable support for LEDs which are connected to GPIO lines. These 54 GPIOs may be on the SoC or some other device which provides GPIOs. 112 which LED is being acted on. As such, the chosen value must be unique 146 identify which LED is being acted on. As such, the chosen value must 181 identify which LED is being acted on. As such, the chosen value must 216 identify which LED is being acted on. As such, the chosen value must 251 identify which LED is being acted on. As such, the chosen value must [all …]
|
| /rk3399_rockchip-uboot/board/freescale/ls2080a/ |
| H A D | README | 18 Booting Linux flavors which do not support 48-bit VA (< Linux 3.18) 20 One needs to use appropriate bootargs to boot Linux flavors which do
|
| /rk3399_rockchip-uboot/arch/arm/mach-imx/ |
| H A D | Kconfig | 46 activate upon a watchdog reset which is nice when iterating 54 This enables the 'dek_blob' command which is used with the 62 This enables the 'hdmidet' command which detects if an HDMI monitor
|
| /rk3399_rockchip-uboot/drivers/mailbox/ |
| H A D | Kconfig | 17 Enable support for a test mailbox implementation, which simply echos 24 This enables support for the NVIDIA Tegra HSP Hw module, which
|
| /rk3399_rockchip-uboot/doc/uImage.FIT/ |
| H A D | source_file_format.txt | 11 booting method which requires that hardware description is available to the 15 replace direct passing of 'struct bd_info' which was used to boot pre-FDT 19 compatibility for platforms which are not FDT ready. Number of elements 55 FIT is formally a flattened device tree (in the libfdt meaning), which 65 help of standard U-Boot mkimage tool which in turn uses dtc (device tree 87 To identify FIT sub-nodes representing images, hashes, configurations (which 164 - data : Path to the external file which contains this node's binary data. 207 convenient, labeled boot configurations, which combine together kernel images 252 "fdt type"). Additional fdt overlay nodes can be supplied which signify 276 The above format shows a 'data' property which holds the data for each image. [all …]
|
| /rk3399_rockchip-uboot/arch/arm/mach-sunxi/ |
| H A D | rmr_switch.S | 8 @ (RMR), which triggers a warm-reset of a core and can request to switch 10 @ The address at which execution starts after the reset is held in the 11 @ RVBAR system register, which is architecturally read-only.
|
| /rk3399_rockchip-uboot/board/congatec/conga-qeval20-qa3-e3845/ |
| H A D | README | 11 provides this console on the UART0 which is provided via a Winbond 19 which is routed from the QSeven SoM to the X300 connector on the
|
| /rk3399_rockchip-uboot/drivers/demo/ |
| H A D | Kconfig | 17 a message when the 'demo hello' command is executed which targets 26 a shape when the 'demo hello' command is executed which targets
|